| Re: [eclipselink-users] osgi dynamic weaving initialization problem |
|
Hi Ted, I hate to be pedantic but you have to follow the wiki instructions _very_ closely. Various people have confirmed the instructions work as written. The last person who posted on the newsgroup having trouble with the example had not followed the wiki example to the letter. For example, if you're trying to boot Equinox with java -jar then it definitely won't work. When started this way, Equinox processes adaptor hooks before it has loaded the EclipseLink framework extension--very frustrating. So far I've had success using the Equinox launcher framework as described on the wiki and with the Spring OSGi test framework which starts Equinox and loads all bundles programatically. Shaun Ted Pricer wrote: I've tried a few times to get dynamic weaving working following the example application [1] The application functions fine, but without any weaving which I tested as recommended: Helper.classImplementsInterface(Person.class, PersistenceWeaved.class) With some use of the debugger it appears to me that hookconfigurators provided by org.eclipse.persistence.jpa.equinox.weaving are not being registered in the HookRegistry. The weaving bundle fragments are resolved as seen in the following osgi short status: 0 ACTIVE org.eclipse.osgi_3.5.0.v20090520 Fragments=4 1 ACTIVE org.eclipse.equinox.common_3.5.0.v20090520-1800 2 RESOLVED org.eclipse.persistence.jpa.equinox_1.1.2.v20090612-r4475 Master=8 3 ACTIVE org.eclipse.persistence.antlr_1.1.2.v20090612-r4475 4 RESOLVED org.eclipse.persistence.jpa.equinox.weaving_1.1.2.v20090612-r4475 Master=0 5 ACTIVE javax.persistence_1.99.0.v200906021518 6 ACTIVE org.eclipse.persistence.asm_1.1.2.v20090612-r4475 7 ACTIVE org.eclipse.update.configurator_3.3.0.v20090312 8 ACTIVE org.eclipse.persistence.jpa_1.1.2.v20090612-r4475 Fragments=2 9 ACTIVE myplugin_1.0.0.qualifier 10 ACTIVE org.eclipse.persistence.core_1.1.2.v20090612-r4475 I have specified the vm argument: -Dosgi.framework.extensions=org.eclipse.persistence.jpa.equinox.weaving But presumably that wouldn't impact the registry of the available hookconfigurators. Is there anything that I maybe did wrong that could be preventing the identification of the hookconfigurators? Am I on the wrong track? Thanks - Ted [1] http://wiki.eclipse.org/EclipseLink/Examples/OSGi/Equinox_Byte_Code_Weaving _______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users --
 Shaun Smith | Principal Product Manager Phone: +19055023094 Oracle Server Technologies, Oracle TopLink ORACLE Canada | 110 Matheson Boulevard West, Suite 100, Mississauga, Ontario | L5R 3P4 
Oracle is committed to developing practices and products that
help protect the environment
|