[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Problem with defining a custom adaptor hook in a framework extension
- From: Thomas Watson <tjwatson@xxxxxxxxxx>
- Date: Mon, 12 Oct 2009 11:08:20 -0500
- Delivered-to: firstname.lastname@example.org
Can you clarify the different ways you launch equinox and what cases fail and what cases succeed? You mention that it fails but that it also succeeds if you add the fragment to the class path while launching with java -jar <equinox.jar>. The equinox launcher (org.eclipse.equinox.launcher jar) is what reads the osgi.framework.extensions property then it sets up the framework class loader with the proper content (the framework + extensions etc.) But if you are not using the equinox launcher (i.e. java -jar <equinox.jar>) then you must add the extension fragments to the class path yourself.
"Kirchev, Lazar" ---10/12/2009 10:29:09 AM---Hello,
"Kirchev, Lazar" <l.kirchev@xxxxxxx>
10/12/2009 10:29 AM
[equinox-dev] Problem with defining a custom adaptor hook in a framework extension
I am trying to define a custom adaptor hook in a framework extension, but it seems as if the hookconfigurators.properties file in the extending fragment bundle jar is not read. When debugging the HooksRegistry code I found that the hookconfigurators.properties file in the bundle is not returned as a resource by the framework classloader.
I have set the osgi.framework.extensions property in the config.ini file, and when starting equinox (I start it with java -jar <equinox.jar>), I add the extension bundle to the classpath. The extension fragment is correctly recognized as such, and gets successfully resolved. The framework and extension bundles are in one and the same folder. I am using 3.5 release.
Any idea what the problem may be?
equinox-dev mailing list