As currently designed and specified, the purpose of Bundle-Classpath is to state the internal classpath of the bundle. That is directories and JAR files contained within the bundle. So Bundle-Classpath must not refer to things out side of the bundle. If you need to refer to things outside of the bundle use Import-Package, Require-Bundle or even fragments.
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] Office: +1 407 849 9117 Mobile: +1 386 848 3788 Niclas Hedhman <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 2006-02-23 07:17 AM Please respond to OSGi Developer Mail List <osgi-dev@bundles.osgi.org> To OSGi Developer Mail List <osgi-dev@bundles.osgi.org> cc Subject [osgi-dev] Non-local classpath entries... Am I allowed to specify http:// URLs in the classpath for a bundle, instead of packaging them within the bundle itself?? How about custom URLs, that may (or not) be resolved either through URLStreamhandlerFactory or the java.protocol.handler.pkgs ?? Cheers Niclas _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
