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

[JBoss JIRA] (JBOSGI-655) Cannot access jboss-osgi API docs

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-655?page=com.atlassian.jira.plugin... ] Thomas Diesler reassigned JBOSGI-655: ------------------------------------- Assignee: Thomas Diesler > Cannot access jboss-osgi API docs > ---------------------------------- > > Key: JBOSGI-655 > URL: https://issues.jboss.org/browse/JBOSGI-655 > Project: JBoss OSGi > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Distribution > Reporter: Thomas Diesler > Assignee: Thomas Diesler > > http://docs.jboss.org/osgi/apidocs > 403 Forbidden > You don't have permission to access /osgi/apidocs on this server. -- 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-725) Add test coverage for ResourceProvisioner service

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-725?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-725. ----------------------------------- Resolution: Done Done > Add test coverage for ResourceProvisioner service > ------------------------------------------------- > > Key: JBOSGI-725 > URL: https://issues.jboss.org/browse/JBOSGI-725 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi > Reporter: Thomas Diesler > Labels: repository > Fix For: JBossOSGi 2.0.1 > > -- 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-682) Add ability to provision adapted modules

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-682?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-682. ----------------------------------- Resolution: Done Done > Add ability to provision adapted modules > ---------------------------------------- > > Key: JBOSGI-682 > URL: https://issues.jboss.org/browse/JBOSGI-682 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi > Reporter: Thomas Diesler > Labels: repository > Fix For: JBossOSGi 2.0.1 > > -- 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-681) Cannot restart webapp bundle after activation failure

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-681?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on JBOSGI-681: ------------------------------------------------ Emmanuel Hugonnet (ehsavoie) <ehugonne(a)redhat.com> made a comment on [bug 959426|https://bugzilla.redhat.com/show_bug.cgi?id=959426] This bug is not linked to OSGI but to org.jboss.ws.common.management.AbstractServerConfig having a stale version of the ServerConfigImpl after the code introduced in https://issues.jboss.org/browse/JBWS-3576 > Cannot restart webapp bundle after activation failure > ----------------------------------------------------- > > Key: JBOSGI-681 > URL: https://issues.jboss.org/browse/JBOSGI-681 > Project: JBoss OSGi > Issue Type: Bug > Components: WildFly > Reporter: Thomas Diesler > Fix For: Awaiting WildFly Support > > > {code} > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) [jboss-msc-1.0.2.GA.jar:1.0.2.GA] > at org.jboss.as.connector.deployers.ra.processors.CachedConnectionManagerSetupProcessor$CachedConnectionManagerSetupAction.setup(CachedConnectionManagerSetupProcessor.java:74) > at org.jboss.as.web.ThreadSetupBindingListener.bind(ThreadSetupBindingListener.java:50) > at org.apache.catalina.core.StandardContext.bindThread(StandardContext.java:4234) > at org.apache.catalina.core.StandardContext.start(StandardContext.java:3740) > at org.jboss.as.web.deployment.WebDeploymentService.start(WebDeploymentService.java:102) > {code} -- 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-734) Provide a Bundle version of the javax.persistence API

by Shelly McGowan (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-734?page=com.atlassian.jira.plugin... ] Shelly McGowan commented on JBOSGI-734: --------------------------------------- The following file should be updated to reference JPA 2.1 artifacts (since the 2.0 artifacts are no longer in the WF8 build). https://github.com/wildfly/wildfly/blob/master/build/src/main/resources/m... > Provide a Bundle version of the javax.persistence API > ----------------------------------------------------- > > Key: JBOSGI-734 > URL: https://issues.jboss.org/browse/JBOSGI-734 > Project: JBoss OSGi > Issue Type: Task > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: jdbc, jpa > Fix For: Awaiting WildFly Support > > > This API is currently provided by hibernate-jpa-2.0-api-1.0.1.Final > Here is an [example|http://mvnrepository.com/artifact/org.eclipse.persistence/javax.p...] -- 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-723) Provide management view for the OSGi Repository

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-723?page=com.atlassian.jira.plugin... ] Thomas Diesler reassigned JBOSGI-723: ------------------------------------- Assignee: Thomas Diesler > Provide management view for the OSGi Repository > ----------------------------------------------- > > Key: JBOSGI-723 > URL: https://issues.jboss.org/browse/JBOSGI-723 > Project: JBoss OSGi > Issue Type: Task > Reporter: Thomas Diesler > Assignee: Thomas Diesler > Labels: roadmap > -- 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-694) Complete support for OSGi Blueprint

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-694?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-694: ---------------------------------- Labels: (was: blueprint roadmap) > Complete support for OSGi Blueprint > ----------------------------------- > > Key: JBOSGI-694 > URL: https://issues.jboss.org/browse/JBOSGI-694 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > R5 TCK compliance for Blueprint -- 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-696) Complete support for OSGi webapp

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-696?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-696: ---------------------------------- Labels: (was: roadmap) > Complete support for OSGi webapp > -------------------------------- > > Key: JBOSGI-696 > URL: https://issues.jboss.org/browse/JBOSGI-696 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > Attachments: webapp-1.0.pdf > > > Following initial support for WAB please review the spec and implement missing functionality. > h5. 128.3.1 WAB Definition > The web.xml must be found with the Bundle findEntries method. The findEntries method includes fragments, allowing the web.xml to be provided by a fragment. > h5. 128.3.2 Starting the Web Application Bundle > The Web Extender should ensure that serving static content from the WAB does not activate the WAB when it has a lazy activation policy. > Validate that the Web-ContextPath manifest header does not match the Context Path of any other currently deployed web application. > h5. 128.3.4 Publishing the Servlet Context > The Web Extender must register the Servlet Context of the WAB as a service, using the Bundle Context of the WAB. > h5. 128.3.5 Static Content > For confidentiality reasons, a Web Runtime must not return any static content for paths that start with one of the following prefixes: > WEB-INF/ > OSGI-INF/ > META-INF/ > OSGI-OPT/ > h5. 128.3.8 Stopping the Web Application Bundle > It is possible that there are one or more colliding WABs because they had the same Context Path as this stopped WAB. If such colliding WABs exists then the Web Extender must attempt to deploy the colliding WAB with the lowest bundle id. > h5. 128.5 Events > * org/osgi/service/web/DEPLOYING The Web Extender has accepted a WAB and started the process of deploying a Web Application. > * org/osgi/service/web/DEPLOYED The Web Extender has finished deploying a Web Application, and the Web Application is now available for web requests on its Context Path. > * org/osgi/service/web/UNDEPLOYING The web extender started undeploying the Web Application in response to its corresponding WAB being stopped or the Web Extender is stopped. > * org/osgi/service/web/UNDEPLOYED The Web Extender has undeployed the Web Application. The application is no longer available for web requests. > * org/osgi/service/web/FAILED The Web Extender has failed to deploy the Web Application, this event can be fired after the DEPLOYING event has fired and indicates that no DEPLOYED event will be fired. > h5. 128.6.1 Bundle Context Access > A Servlet can obtain a Bundle Context as follows: > {code} > BundleContext ctxt = (BundleContext) > servletContext.getAttribute(osgi-bundlecontext); > {code} > h5. 128.6.3 Resource Lookup > The getResource and getResourceAsStream methods of the ServletContext interface are used to access resources in the web application. For a WAB, these resources must be found according to the findEntries method, this method includes fragments. > The getResourcePaths method must map to the Bundle getEntryPaths method, its return type is a Set and can not handle multiples. However, the paths from the getEntryPaths method are relative while the methods of the getResourcePaths must be absolute. > h5. 128.6.5 JavaServer Pages Support > The Web Runtime can construct a special class loader to load generated JSP > classes such that classes from the bundle class path are visible to newly compiled JSP classes. > 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-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: ---------------------------------- Labels: (was: cdi roadmap) > Initial OSGi / CDI Integration > ------------------------------- > > Key: JBOSGI-699 > URL: https://issues.jboss.org/browse/JBOSGI-699 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > 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-692) Complete support for OSGi JTA

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-692?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-692: ---------------------------------- Labels: (was: roadmap) > Complete support for OSGi JTA > ----------------------------- > > Key: JBOSGI-692 > URL: https://issues.jboss.org/browse/JBOSGI-692 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > R5 TCK compliance for JTA -- 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