Re: [hibernate-dev] Hibernate Search 3.4 release train

Its a minor change but I would like to make a small enhancement to EntityManager.unwrap(). I would like to support SessionFactory in case I want to use it later in AS7... Is this completely silly or just mildly silly? If creating a container managed entity manager doesn't consume a database connection. I propose that its just mildly silly. If its just mildly silly, I might want to use the unwrap functionality to keep the AS injection code generic (covering injecting a PU into a Hibernate SessionFactory). Of course, the other silly part is the idea that I would get an EM from the PU (could lead to unexpected errors if something goes wrong). It might be nice to have an unwrap method on the EntityManagerFactory for this purpose. Is that worth proposing for a future JPA release? On 02/16/2011 08:46 AM, Emmanuel Bernard wrote: > Hi, > We have targeted v 3.4 for end of march. > What do you think of doing an Alpha1 within the next two weeks? > > For reference, the list of todo we had for 3.4 is: > - Use 2LC for object load (emmanuel, done) > - Tx and JMS (sanne) > - Faceting (hardy) > - Benchmark (sanne, not sure what the detail was) > - FieldCache usage (sanne) > - Abstract from Core (emmanuel) > > We also already have a few bug fixes and a few non planned new features: > - multi-threads used in text analysis for MassIndexer > - Infinispan 4.2.1 (CR1) > - index on indexed entity change > - MassIndexer monitoring > > Which feature do you think can go into Alpha1? > > Emmanuel > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev