went a step further trying to manage the path of the module. the point i don't really know if about resources, we probably need a special thing for it: jndi names are not more correct when re-reading the conf.
containers should be updated too. Note: to be able to use xml as format for th einfo tree i had to add some jaxb annotation to EjbJarInfo (List<EnterpriseBeanInfo> needs inheritance informations to be unmarshable), i'm not sure such a change is ok or not - Romain 2012/2/13 Romain Manni-Bucau <[email protected]> > Idea: dump info tree in a file in the app at build time (mvn for the first > version) then at runtime simply read this file (skip scanning etc...) > > Starting code: > https://svn.apache.org/repos/asf/openejb/trunk/maven-plugins/info-maven-plugin/ > > Still need a lot of enhancement but any help/ideas are welcome ;) > > Current issues: > 1) what to do about paths -> override them after having read the info tree? > 2) how to replace all the info tree in the current core, it seems it is > not so easy (to do so for EJBContainers and TomEE for instance since the > API usage is different), any preferred place for such a change? > > - Romain >
