[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] [Aspects] AOSGi without Eclipse


Tom,

Thanks for the quick reply. The EclipseStarter was being used directly when the problem occured. I have opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=170881 as suggested.

Cheers

Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM Hursley Park, Winchester,  SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
http://w3.hursley.ibm.com/~websterm/



Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

17/01/2007 15:51

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] [Aspects] AOSGi without Eclipse






In the framework we currently assume that framework extensions that provide framework hooks are installed as framework fragments.  The OSGi spec mandates that framework fragments must be appended to the classpath of the framework's classloader.  The bootstrap launcher (the old startup.jar) always ensures that the org.eclipse.osgi.jar is the first thing on the classpath for the framework's classloader.  If you are not using the bootstrap launcher to launch the framework then you must set your classpath correctly so that the org.eclipse.osgi.jar is first.


With that said, we could make this easier by marking the resource provided by the framework as special and ensure that we process it first.  Perhaps you should open a bug against Equinox->Framework so we can discuss and consider this.


Thanks.


Tom



Matthew Webster <matthew_webster@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

01/17/2007 08:53 AM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] [Aspects] AOSGi without Eclipse








>The NPE occurs because my StorageHook, rightly or wrongly, needs to be called _after_ the Equinox one. That hook initializes the BundleData in particular the
>symbolicName. The order in which hooks are created and called depends on CLASSPATH.
The order in which hooks, that are contributed by different bundles, depends on CLASSPATH rather than any other explicit control (because of the use of ClassLoader.getResources()). In particular system provided hooks, whose contribution others may rely on, may not be invoked first. Was this intended? Is this bad practice on my part? If I don't rely on the default hooks I will have to parse the manifest myself which seems wrong.


Thanks


Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM Hursley Park, Winchester,  SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal)
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
http://w3.hursley.ibm.com/~websterm/
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev