The answer is yes. Bundles must import any package that is not from one of the java.* packages. I suspect this is working for the default equinox configuration because we have a compatibility flag enabled by default that does a boot delegation as a last resort. Could you please open an eclipse orbit bug for this at: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Orbit
Tom |------------> | From: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Raymond Auge <[email protected]> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | To: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Equinox development mailing list <[email protected]>, | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Date: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |09/12/2012 02:42 PM | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Subject: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: [equinox-dev] org.xml.sax | >--------------------------------------------------------------------------------------------------------------------------------------------------| excerpt of log: BundleLoader[org.apache.jasper.glassfish_2.2.2.v201112011158] found local class org.apache.jasper.compiler.Node$Root BundleClassLoader [org.apache.jasper.glassfish_2.2.2.v201112011158].loadClass (org.xml.sax.Attributes) BundleLoader [org.apache.jasper.glassfish_2.2.2.v201112011158].loadBundleClass (org.xml.sax.Attributes) BundleLoader [org.apache.jasper.glassfish_2.2.2.v201112011158].findLocalClass (org.xml.sax.Attributes) BundleClassLoader [/home/rotty/AS/liferay-portal/data/framework/state/org.eclipse.osgi/bundles/69/1/bundlefile].findClassImpl (org.xml.sax.Attributes) BundleClassLoader [org.apache.jasper.glassfish_2.2.2.v201112011158].loadClass (org.xml.sax.Attributes) failed. java.lang.ClassNotFoundException: org.xml.sax.Attributes at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal (BundleLoader.java:501) at org.eclipse.osgi.internal.loader.BundleLoader.findClass (BundleLoader.java:421) at org.eclipse.osgi.internal.loader.BundleLoader.findClass (BundleLoader.java:412) at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass (DefaultClassLoader.java:107) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at org.apache.jasper.compiler.ParserController.doParse (ParserController.java:244) at org.apache.jasper.compiler.ParserController.parse (ParserController.java:145) at org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:212) at org.apache.jasper.compiler.Compiler.compile(Compiler.java:451) at org.apache.jasper.JspCompilationContext.compile (JspCompilationContext.java:625) at org.apache.jasper.servlet.JspServletWrapper.service (JspServletWrapper.java:374) at org.apache.jasper.servlet.JspServlet._serviceJspFile (JspServlet.java:492) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:378) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) - Ray On Wed, Sep 12, 2012 at 3:40 PM, Raymond Auge <[email protected]> wrote: Do bundles have to declare this import? It appears that it's a default package exported by the system bundle. However, if you take a look at this bundle org.apache.jasper.glassfish_2.2.2.v201112011158 it does not declare that package as an import, but still fails to resolve it as well. Thoughts? I'm testing to see if I can solve this by attaching a fragment bundle which imports the package. -- Raymond Augé | Senior Software Architect | Liferay, Inc. --- 8-9 October 2012 | Liferay North America Symposium | liferay.com/northamerica2012 16-17 October 2012 | Liferay Europe Symposium | liferay.com/europe2012 24-25 October 2012 | Liferay Spain Symposium | liferay.com/spain2012 -- Raymond Augé | Senior Software Architect | Liferay, Inc. --- 8-9 October 2012 | Liferay North America Symposium | liferay.com/northamerica2012 16-17 October 2012 | Liferay Europe Symposium | liferay.com/europe2012 24-25 October 2012 | Liferay Spain Symposium | liferay.com/spain2012 _______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
_______________________________________________ equinox-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/equinox-dev
