Furthermore pre-packaged modules such as ADMIN, USERS, MESSAGING and SCHEDULER-QUARTZ needed to self-execute the enhancement in order to put persistence capable classes inside the JAR. This was a mess if you needed to change the ORM binding since anything resided inside the JAR.
I have to check yet if run-time changes to the entity POJOs are auto-enhanced at the fly... If works the productivity would be speedup over and over again.
Thanks to Andy Jefferson of DataNucleus team in supporting my crazy requestes :-) The work tomorrow will be in changing all the wizards to support the new configuration. In few words the change consist in:
- Let to the PersistenceAspect to invoke the Enhancer at startup
- Create the file persistence.xml inside the src/META-INF folder.
2 comments:
I'm trying to do the same thing. Do you have a sample of how to perform the runtime enhancement using the API?
At the end my patch wont work, sorry. But I don't work on that since that post.
Post a Comment