Hi, I'll give it a try tomorrow !
Other options I found were hibernate specific, I guess the undocumented option "hibernate.query.startup_check" will bring the most boost during the start up; I have hundreds of named queries... Probably the mapping constraint checks could not skipped due the nature of a consistent persistence factory. Other options, no clue if they would have any impact on the initialisation part, I will test too: hibernate.bytecode.provider=cglib|javassist hibernate.bytecode.use_reflection_optimizer=true|false https://hibernate.atlassian.net/browse/HHH-2193 hibernate.query.startup_check true/false I think we are done, thank you! Kind regards, Andreas -- View this message in context: http://openejb.979440.n4.nabble.com/ApplicationComposer-JUnit-EJB-Tests-autoscanning-issue-and-Hibernate-tp4663182p4663231.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
