29 | How prevent post-compile enhancement of non entity classesI have recently moved to post-compile enhancement (from automatic run-time enhancement) using ... the enhancer on entity files. For full project build the following works, by grouping entities ... /objectdb.jar"/> <target name="-post-compile"> <echo message="begin ObjectDB enhancer"/> <java |
29 | Enhancer problemDuring development, I have used the enhancer API in a static block in the code that creates the EntityManagerFactory, ie. com.objectdb.Enhancer.enhance("com.fastmodel.fastplan.entities.*"); com.objectdb.Enhancer.enhance("com.fastmodel.fastplan.entities.comm.*"); com.objectdb.Enhancer.enhance |
29 | Custom Classloader: Issues with the Enhancer Agent); }else{ throw new ClassNotFoundException(); } } } This works great without the Enhancer Agent ... my call to defineClass(), makes the enhancement to the class and loads the modified version in memory ... ()/findClass()/...) as part of the enhancement process, resulting in a recursive call to my custom |
28 | Request clarification of changes to accessor enhancement policy (non-getter prefix instead of getter suffix) AND annotations were made to the way enhancement treats getters and setters (property accessors), namely there are no longer enhanced additional getters/setters, because the additional methods now use (since about version 2-6-5 ... for various tasks, including for diagnosing whether enhancement has indeed taken place, leading |
28 | ObjectDB with JRebel: copious 'Not Enhanced:' errors with EJBs enhancer.agent] Not Enhanced: com/example/ejb/query/__EJB31_Generated__ExampleQuery__Intf__: com ... .SCM.w(SCM.java:455) ... 76 more Severe: [2016-10-30 09:16:46 #6 enhancer.agent] I am using post-compile ObjectDB enhancement in an Ant script that targets folders with @Entity classes only. webel |
28 | OEM Enhancer causing Jenkins job to freezeHi all, We are using ODB enhancer in one of our jobs on jenkins, built via ant. Recently we started ... }/temp/*;${dist.dir}" classname="com.objectdb.Enhancer" fork="true"> <arg line="-s ${dist.dir}/our/entities/package/"/> </java> Is it possible to enable some detailed logging for enhancer |
28 | ObjectDB Enhancer Tool in Java 9 to run com.objectdb.Enhancer from that module, but ObjectDB gives the error below. My guess is the error ... =ObjectDb.conf --module-path com.objectdb.jar --module com.objectdb/com.objectdb.Enhancer Command ... ) at com.objectdb/com.objectdb.o.JEN.<init>(JEN.java:67) at com.objectdb/com.objectdb.Enhancer.main |
5 | Enhancement does not show an error message when an outdated license is used2.8.7.b08 Accidentally we used an outdated ObjectDB license, if we enhance the entities. The entities were not enhanced in our jars. But the message from the enhancement tool com.objectdb.Enhancer shows that all entites are enhanced. Can you throw an error message, if the license is outdated? btc |
5 | Enhancer option -s works not as expectedWe found a bug in the enhancer with the option -s . Given structure: com |- btc |- |- base ... |- |- |- |- subpackage |- |- |- |- |- Entity2.class ... com.objectdb.Enhancer -noaware -s com.btc.base.impl.* Entity1 and Entity2 enhanced as expected. ... com.objectdb.Enhancer |
5 | Updating JPA Entity Objects on commit. A more efficient way to detect changes automatically is described in the Enhancer section ... classes are enhanced. Therefore, for efficiency purposes, the default behavior of ObjectDB ignores array changes when using enhanced entity classes: Employee employee = em.find(Employee.class, 1 |
