July 2013 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] (JBOSGI-735) HttpService MimeType, ContentLength, etc

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-735?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-735: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > HttpService MimeType, ContentLength, etc > ---------------------------------------- > > Key: JBOSGI-735 > URL: https://issues.jboss.org/browse/JBOSGI-735 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-740) HttpService TCK testBundleStopping() failing

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-740?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-740: ---------------------------------- Component/s: HttpService WildFly > HttpService TCK testBundleStopping() failing > -------------------------------------------- > > Key: JBOSGI-740 > URL: https://issues.jboss.org/browse/JBOSGI-740 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: David Bosschaert > > The OSGi HTTP Service TCK test testBundleStopping() fails with the following exception: > {code}org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: tb1:4.2.0 > at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:110) > at org.jboss.as.osgi.service.BundleLifecycleIntegration.start(BundleLifecycleIntegration.java:181) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:292) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:228) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:522) > at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) > Caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.osgi.service.http.HttpService.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/internal/HostBundleClassLoader) of the current class, org/osgi/test/cases/http/tb1/HttpTestBundle2, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/osgi/service/http/HttpService, have different Class objects for the type javax/servlet/Servlet used in the signature > at org.osgi.test.cases.http.tb1.HttpTestBundle2.start(HttpTestBundle2.java:30) > at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:84) > ... 10 more{code} > Seems like a resolution error, it could be related to how the TCK is set up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-739) Http Service TCK testLongRegistrationName() failing

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-739?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-739: ---------------------------------- Component/s: HttpService WildFly > Http Service TCK testLongRegistrationName() failing > --------------------------------------------------- > > Key: JBOSGI-739 > URL: https://issues.jboss.org/browse/JBOSGI-739 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: David Bosschaert > > The OSGi HTTP Service TCK test testLongRegistrationName() fails with the following exception: > java.io.FileNotFoundException: http://localhost:8080/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy... > Apparently there is an issue with long registration names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-735) HttpService MimeType, ContentLength, etc

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-735?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-735: ---------------------------------- Component/s: HttpService WildFly > HttpService MimeType, ContentLength, etc > ---------------------------------------- > > Key: JBOSGI-735 > URL: https://issues.jboss.org/browse/JBOSGI-735 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-738) HttpService configurable virtual host/port

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-738?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-738: ---------------------------------- Component/s: HttpService WildFly > HttpService configurable virtual host/port > ------------------------------------------ > > Key: JBOSGI-738 > URL: https://issues.jboss.org/browse/JBOSGI-738 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-738) HttpService configurable virtual host/port

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-738?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-738: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > HttpService configurable virtual host/port > ------------------------------------------ > > Key: JBOSGI-738 > URL: https://issues.jboss.org/browse/JBOSGI-738 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: Thomas Diesler > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-740) HttpService TCK testBundleStopping() failing

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-740?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-740: ---------------------------------- Summary: HttpService TCK testBundleStopping() failing (was: Http Service TCK testBundleStopping() failing) > HttpService TCK testBundleStopping() failing > -------------------------------------------- > > Key: JBOSGI-740 > URL: https://issues.jboss.org/browse/JBOSGI-740 > Project: JBoss OSGi > Issue Type: Sub-task > Reporter: David Bosschaert > > The OSGi HTTP Service TCK test testBundleStopping() fails with the following exception: > {code}org.osgi.framework.BundleException: JBOSGI011254: Cannot start bundle: tb1:4.2.0 > at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:110) > at org.jboss.as.osgi.service.BundleLifecycleIntegration.start(BundleLifecycleIntegration.java:181) > at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:292) > at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:228) > at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:522) > at org.jboss.as.osgi.deployment.BundleActivateProcessor$BundleActivateService.start(BundleActivateProcessor.java:127) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:680) > Caused by: java.lang.LinkageError: loader constraint violation: when resolving interface method "org.osgi.service.http.HttpService.registerServlet(Ljava/lang/String;Ljavax/servlet/Servlet;Ljava/util/Dictionary;Lorg/osgi/service/http/HttpContext;)V" the class loader (instance of org/jboss/osgi/framework/internal/HostBundleClassLoader) of the current class, org/osgi/test/cases/http/tb1/HttpTestBundle2, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for resolved class, org/osgi/service/http/HttpService, have different Class objects for the type javax/servlet/Servlet used in the signature > at org.osgi.test.cases.http.tb1.HttpTestBundle2.start(HttpTestBundle2.java:30) > at org.jboss.osgi.framework.internal.DefaultBundleLifecycleHandler.start(DefaultBundleLifecycleHandler.java:84) > ... 10 more{code} > Seems like a resolution error, it could be related to how the TCK is set up. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-739) Http Service TCK testLongRegistrationName() failing

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-739?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-739: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Http Service TCK testLongRegistrationName() failing > --------------------------------------------------- > > Key: JBOSGI-739 > URL: https://issues.jboss.org/browse/JBOSGI-739 > Project: JBoss OSGi > Issue Type: Sub-task > Reporter: David Bosschaert > > The OSGi HTTP Service TCK test testLongRegistrationName() fails with the following exception: > java.io.FileNotFoundException: http://localhost:8080/abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxy... > Apparently there is an issue with long registration names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-699) Initial OSGi / CDI Integration

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-699?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-699: ---------------------------------- Component/s: CDI > Initial OSGi / CDI Integration > ------------------------------- > > Key: JBOSGI-699 > URL: https://issues.jboss.org/browse/JBOSGI-699 > Project: JBoss OSGi > Issue Type: Feature Request > Components: CDI > Reporter: Thomas Diesler > Labels: roadmap > > Provide an example test that shows CDI integration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBOSGI-688) Complete runtime support for Karaf based products

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-688?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-688. ----------------------------------- Resolution: Won't Fix > Complete runtime support for Karaf based products > ------------------------------------------------- > > Key: JBOSGI-688 > URL: https://issues.jboss.org/browse/JBOSGI-688 > Project: JBoss OSGi > Issue Type: Feature Request > Reporter: Thomas Diesler > Labels: roadmap > > Provide complete support for Karaf based products -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013