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

[JBoss JIRA] (JBOSGI-720) Complete support for HttpService

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-720?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-720: ---------------------------------- Component/s: HttpService WildFly > Complete support for HttpService > -------------------------------- > > Key: JBOSGI-720 > URL: https://issues.jboss.org/browse/JBOSGI-720 > Project: JBoss OSGi > Issue Type: Task > Components: HttpService, WildFly > Reporter: Thomas Diesler > Labels: roadmap > > #1 Add support for MimeType, Content-Lenght, etc > #2 Delegate authentication/authorisation to HttpContext > #3 Add support for "/" root context > #4 Make HttpService an optional capability > #5 Make virtual host/port configurable > This issue is complete when the TCK passes -- 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-720) Complete support for HttpService

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-720?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-720: ---------------------------------- Summary: Complete support for HttpService (was: Complete support for HttpService on JBossWeb) > Complete support for HttpService > -------------------------------- > > Key: JBOSGI-720 > URL: https://issues.jboss.org/browse/JBOSGI-720 > Project: JBoss OSGi > Issue Type: Task > Reporter: Thomas Diesler > Labels: roadmap > > #1 Add support for MimeType, Content-Lenght, etc > #2 Delegate authentication/authorisation to HttpContext > #3 Add support for "/" root context > #4 Make HttpService an optional capability > #5 Make virtual host/port configurable > This issue is complete when the TCK passes -- 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-715) 128.5 Events

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-715?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-715: ---------------------------------- Component/s: WebApp WildFly > 128.5 Events > ------------ > > Key: JBOSGI-715 > URL: https://issues.jboss.org/browse/JBOSGI-715 > Project: JBoss OSGi > Issue Type: Sub-task > Components: WebApp, WildFly > Reporter: David Bosschaert > -- 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-741) Make the root context of all HttpService-registered entities configurable

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-741?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-741: ---------------------------------- Component/s: HttpService WildFly > Make the root context of all HttpService-registered entities configurable > ------------------------------------------------------------------------- > > Key: JBOSGI-741 > URL: https://issues.jboss.org/browse/JBOSGI-741 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: David Bosschaert > -- 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-717) 128.6.3 Resource Lookup

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-717?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-717: ---------------------------------- Component/s: WebApp WildFly > 128.6.3 Resource Lookup > ----------------------- > > Key: JBOSGI-717 > URL: https://issues.jboss.org/browse/JBOSGI-717 > Project: JBoss OSGi > Issue Type: Sub-task > Components: WebApp, WildFly > Reporter: David Bosschaert > -- 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-718) 128.6.5 JSP Support

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-718?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-718: ---------------------------------- Component/s: WebApp WildFly > 128.6.5 JSP Support > ------------------- > > Key: JBOSGI-718 > URL: https://issues.jboss.org/browse/JBOSGI-718 > Project: JBoss OSGi > Issue Type: Sub-task > Components: WebApp, WildFly > Reporter: David Bosschaert > -- 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: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > 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-500) Pass JNDI CT

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-500?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-500: ---------------------------------- Component/s: WildFly > Pass JNDI CT > ------------ > > Key: JBOSGI-500 > URL: https://issues.jboss.org/browse/JBOSGI-500 > Project: JBoss OSGi > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JNDI, WildFly > Reporter: David Bosschaert > -- 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-741) Make the root context of all HttpService-registered entities configurable

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-741?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-741: ---------------------------------- Comment: was deleted (was: Won't Fix - OSGi is going to get removed) > Make the root context of all HttpService-registered entities configurable > ------------------------------------------------------------------------- > > Key: JBOSGI-741 > URL: https://issues.jboss.org/browse/JBOSGI-741 > Project: JBoss OSGi > Issue Type: Sub-task > Components: HttpService, WildFly > Reporter: David Bosschaert > -- 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-711) 128.3.2 Starting the Web Application Bundle

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-711?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-711: ---------------------------------- Component/s: WebApp WildFly > 128.3.2 Starting the Web Application Bundle > ------------------------------------------- > > Key: JBOSGI-711 > URL: https://issues.jboss.org/browse/JBOSGI-711 > Project: JBoss OSGi > Issue Type: Sub-task > Components: WebApp, WildFly > Reporter: David Bosschaert > > The Web Extender should ensure that serving static content from the WAB does not activate the WAB when it has a lazy activation policy. -- 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