November 2010 - jboss-osgi-issues

[JBoss JIRA] Created: (JBOSGI-370) Initial support for URLStreamHandlerService

by Thomas Diesler (JIRA)

Initial support for URLStreamHandlerService ------------------------------------------- Key: JBOSGI-370 URL: https://jira.jboss.org/browse/JBOSGI-370 Project: JBoss OSGi Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-427) Unify Bundle install paths

by Thomas Diesler (JIRA)

Unify Bundle install paths -------------------------- Key: JBOSGI-427 URL: https://jira.jboss.org/browse/JBOSGI-427 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Thomas Diesler There are multiple code paths paths that install a bundle Aries JMX instlall --> BundleContext.install() BundleContext.install() -> BundleManager.install(Deployment) DeploymentUnitProcessor --> DeployerService.deploy(Deployment) Bundle Hotdeploy --> DeployerService.deploy(Deployment) OSGi Console --> DeployerService.deploy(Deployment) DeployerService.deploy(Deployment) --> BundleManager.install(Deployment) In AS7 all bundle install paths must go through the DeploymentChain -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-426) Use AS7 Arquillian subsystem instead of the arquillian-osgi-bundle

by Thomas Diesler (JIRA)

Use AS7 Arquillian subsystem instead of the arquillian-osgi-bundle ------------------------------------------------------------------ Key: JBOSGI-426 URL: https://jira.jboss.org/browse/JBOSGI-426 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler There needs to be a unique entry point for ARQ tests in AS7. \ Currently it is not possible to run ARQ OSGi bundle tests on the Arquillian subsystem. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-421) Provide singned versions of the osgi archives

by Thomas Diesler (JIRA)

Provide singned versions of the osgi archives --------------------------------------------- Key: JBOSGI-421 URL: https://jira.jboss.org/browse/JBOSGI-421 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta11 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-398) Profile framework startup and bundle deployment

by Thomas Diesler (JIRA)

Profile framework startup and bundle deployment ----------------------------------------------- Key: JBOSGI-398 URL: https://jira.jboss.org/browse/JBOSGI-398 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta10 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-420) Unexpected null wiring for JAXBContext

by Thomas Diesler (JIRA)

Unexpected null wiring for JAXBContext -------------------------------------- Key: JBOSGI-420 URL: https://jira.jboss.org/browse/JBOSGI-420 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta10 For target.container jboss700, jboss701 testWiring(org.jboss.test.osgi.example.xml.jaxb.JAXBTestCase) Time elapsed: 0.166 sec <<< FAILURE! java.lang.AssertionError: jboss-osgi-jaxb expected:<jboss-osgi-jaxb:2.1.10.SP5> but was:<null> at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.failNotEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:126) at org.jboss.test.osgi.example.xml.jaxb.JAXBTestCase.testWiring(JAXBTestCase.java:99) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] Created: (JBOSGI-416) WebApp Bundle and example-webapp.war doesn't start

by David Bosschaert (JIRA)

WebApp Bundle and example-webapp.war doesn't start -------------------------------------------------- Key: JBOSGI-416 URL: https://jira.jboss.org/browse/JBOSGI-416 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-webapp Affects Versions: JBossOSGi 1.0.0 Beta9 Reporter: David Bosschaert Reported by Kit Plummer: http://community.jboss.org/thread/158370 I'm trying to deploy an OSGi'ed WAR. I thought it was just my WAR, but the example-webapp.war causes the same errors. 14:26:13,000 ERROR [jboss-osgi-webconsole] Cannot start org.apache.felix.log.LogException: org.osgi.framework.BundleException: Cannot start bundle: example-webapp:0.0.0 at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:245) at org.jboss.osgi.framework.bundle.AbstractBundle.start(AbstractBundle.java:469) at org.jboss.osgi.framework.bundle.BundleWrapper.start(BundleWrapper.java:166) at org.apache.felix.webconsole.internal.core.BundlesServlet.doPost(BundlesServlet.java:147) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.felix.webconsole.internal.servlet.OsgiManager.service(OsgiManager.java:329) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:389) at org.ops4j.pax.web.service.jetty.internal.HttpServiceServletHandler.handle(HttpServiceServletHandler.java:64) at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765) at org.ops4j.pax.web.service.jetty.internal.HttpServiceContext.handle(HttpServiceContext.java:111) at org.ops4j.pax.web.service.jetty.internal.JettyServerHandlerCollection.handle(JettyServerHandlerCollection.java:64) at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:326) at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:534) at org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:879) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:747) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:218) at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404) at org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409) at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520) Caused by: org.apache.felix.log.LogException: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.DocumentBuilderFactoryImpl not found at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:129) at org.ops4j.util.xml.ElementHelper.getRootElement(ElementHelper.java:68) at org.ops4j.pax.web.extender.war.internal.parser.dom.DOMWebXmlParser.parse(DOMWebXmlParser.java:63) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.createWebAppMetadata(WebXMLParserInterceptor.java:82) at org.jboss.osgi.webapp.internal.WebXMLParserInterceptor.invoke(WebXMLParserInterceptor.java:67) at org.jboss.osgi.deployment.interceptor.AbstractLifecycleInterceptorService.handleStateChange(AbstractLifecycleInterceptorService.java:279) at org.jboss.osgi.framework.plugin.internal.LifecycleInterceptorPluginImpl.handleStateChange(LifecycleInterceptorPluginImpl.java:106) at org.jboss.osgi.framework.bundle.AbstractBundle.changeState(AbstractBundle.java:443) at org.jboss.osgi.framework.bundle.HostBundle.startInternal(HostBundle.java:192) ... 22 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues November 2010