Cody Lerum
Cody Lerum
Chrome Launch Issue: https://code.google.com/p/chromium/issues/detail?id=437908
This is a pretty common issue with maven caches. If you have a dependency of foo-1.0.0.jar and then upgrade to foo-1.0.1.jar the original foo-1.0.0.jar will stay in the cache forever....
Created issue at ee4j https://github.com/eclipse-ee4j/mojarra/issues/4500
com.google.common.collect.TreeBasedTable#rowKeySet returns SortedSet rather than NavigableSet Perhaps these can be excluded?
@kluever Perfect, I guess that means no PR for me to write. I'll keep an eye out for it to arrive.
This was done in DeltaSpike with an `@PersistenceUnit EntityManagerFactory` but that utilized its own Transactions module to handle the synchronization of the EntityManager to the Transaction. See - https://deltaspike.apache.org/jpa.html
@arun-gupta I have an example here https://github.com/codylerum/eebox/tree/requestscoped_em that shows the issue. (use the requestscoped_em branch) There is an link to both the working and the broken from the context root...
@arun-gupta Thanks. Let me know if there is anything else I can do to move this along.
@arun-gupta Arun FWIW this does appear to have the same behavior with Glassfish as it does with wildfly.
@scottmarlow The EM detaches everything after the first tx completes. If I use ``` @PersistenceUnit private EntityManagerFactory entityManagerFactory; @Produces @RequestScoped public EntityManager entityManager() { log.infof("Producing Entity Manager"); return entityManagerFactory .createEntityManager(SynchronizationType.SYNCHRONIZED);...