[ https://issues.apache.org/jira/browse/JDO-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Jefferson updated JDO-591: ------------------------------- Attachment: jdoenhancer-3.patch Updated patch adding JDOHelper.getEnhancer() method taking in class loader to load the enhancer from; searches for "META-INF/services/javax.jdo.JDOEnhancer" file in CLASSPATH. > Enhancer Invocation API > ----------------------- > > Key: JDO-591 > URL: https://issues.apache.org/jira/browse/JDO-591 > Project: JDO > Issue Type: New Feature > Components: api2 > Reporter: Andy Jefferson > Assignee: Andy Jefferson > Fix For: JDO 2 maintenance release 3 > > Attachments: jdoenhancer-3.patch > > > Having a standard interface to invoke the enhancer makes a lot of sense so we > can have interchangeability of enhancers (for implementations that support > BinaryCompatibility). > A start point (for discussions) could be > java -cp classpath {enhancer-class} [options] [jdo-files] [class-files] > where options can be > -persistenceUnit persistence-unit-name : Name of a "persistence-unit" > to enhance the classes for > -d target-dir-name : Write the enhanced classes to the specified > directory > -checkonly : Just check the classes for enhancement status > -v : verbose output > This then allows enhancement of the specified classes, or the classes defined > by the specified JDO files, or the classes defined by the specified > persistence-unit. > What other control would people like to see ? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.