[JBoss JIRA] Resolved: (JBOSGI-5) OSGi Deployers
by Thomas Diesler (JIRA)
[ https://jira.jboss.org/jira/browse/JBOSGI-5?page=com.atlassian.jira.plugi... ]
Thomas Diesler resolved JBOSGI-5.
---------------------------------
Fix Version/s: (was: JBossOSGi 1.0.x)
Resolution: Out of Date
Out of Date
> OSGi Deployers
> --------------
>
> Key: JBOSGI-5
> URL: https://jira.jboss.org/jira/browse/JBOSGI-5
> Project: JBoss OSGi
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Core
> Reporter: Adrian Brock
>
> Holder task for OSGi aspectized deployers.
> The deployers will include at least:
> 1) Structure deployer to recognise OSGi bundles and setup "subdeployments" according to the jars
> specified in the osgi classpath.
> 2) OSGi parser deployer that turns the manifest entries into an OSGIMetaData model
> 3) DeploymentResolver that sets up the dependencies for deployments
> 4) OSGi classloader deployer - replacement for UCL classloader with OSGi classloading semantics
> 5) OSGi real deployer - creates a bean that provides an OSGi facade (the lifecycle)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months
[JBoss JIRA] Created: (JBOSGI-92) XMLParserActivator in compendium cantot load SAXParserFactory
by Thomas Diesler (JIRA)
XMLParserActivator in compendium cantot load SAXParserFactory
-------------------------------------------------------------
Key: JBOSGI-92
URL: https://jira.jboss.org/jira/browse/JBOSGI-92
Project: JBossOSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Compendium
Reporter: Thomas Diesler
Fix For: Continuing
The XercesParserActivator fails with
Caused by: javax.xml.parsers.FactoryConfigurationError: java.lang.ClassNotFoundException: *** Class 'org.apache.xerces.jaxp.SAXParserFactoryImpl' was not found because bundle 1 does not import 'org.apache.xerces.jaxp' even though bundle 4 does export it. Additionally, the class is also available from the system class loader. There are two fixes: 1) Add an import for 'org.apache.xerces.jaxp' to bundle 1; imports are necessary for each class directly touched by bundle code or indirectly touched, such as super classes if their methods are used. 2) Add package 'org.apache.xerces.jaxp' to the 'org.osgi.framework.bootdelegation' property; a library or VM bug can cause classes to be loaded by the wrong class loader. The first approach is preferable for preserving modularity. ***
at org.osgi.util.xml.XMLParserActivator.getFactory(XMLParserActivator.java:459)
at org.osgi.util.xml.XMLParserActivator.registerSAXParsers(XMLParserActivator.java:237)
at org.osgi.util.xml.XMLParserActivator.start(XMLParserActivator.java:146)
at org.jboss.osgi.apache.xerces.internal.XercesParserActivator.start(XercesParserActivator.java:50)
at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:589)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1458)
which is caused by
Class.forName(parserFactoryClassName).newInstance()
in the compendium jar
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 11 months