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

[JBoss JIRA] (JBOSGI-583) Move JBOSGi downloads to jboss.org

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-583?page=com.atlassian.jira.plugin... ] Thomas Diesler resolved JBOSGI-583. ----------------------------------- Resolution: Won't Fix Won't Fix > Move JBOSGi downloads to jboss.org > ---------------------------------- > > Key: JBOSGI-583 > URL: https://issues.jboss.org/browse/JBOSGI-583 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Distribution > 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-280) Add security option for native library deployment

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-280?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-280: ---------------------------------- Fix Version/s: Awaiting Volunteers > Add security option for native library deployment > ------------------------------------------------- > > Key: JBOSGI-280 > URL: https://issues.jboss.org/browse/JBOSGI-280 > Project: JBoss OSGi > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Core Framework > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > Adrian says: > It might be a good idea to add a "security option" for this feature.. > e.g. something like only signed jars can deploy native code this way. > i.e. have a new security permission for this feature (with the option on the deployer to enable/disable the check). -- 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: ---------------------------------- Fix Version/s: Awaiting Volunteers > 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: Enterprise OSGi, WildFly > Reporter: David Bosschaert > Fix For: Awaiting Volunteers > > > 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

[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: ---------------------------------- Fix Version/s: Awaiting Volunteers > 128.6.3 Resource Lookup > ----------------------- > > Key: JBOSGI-717 > URL: https://issues.jboss.org/browse/JBOSGI-717 > Project: JBoss OSGi > Issue Type: Sub-task > Components: Enterprise OSGi, WildFly > Reporter: David Bosschaert > Fix For: Awaiting Volunteers > > -- 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-733) Complete implementation of the FrameworkFactory

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-733?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-733: ---------------------------------- Fix Version/s: Awaiting Volunteers > Complete implementation of the FrameworkFactory > ----------------------------------------------- > > Key: JBOSGI-733 > URL: https://issues.jboss.org/browse/JBOSGI-733 > Project: JBoss OSGi > Issue Type: Task > Components: Core Framework, WildFly > Reporter: David Bosschaert > Labels: roadmap > Fix For: Awaiting Volunteers > > > The OSGi CT is currently run with the JBoss OSGi framework standalone. It should also be possible to run the CT with the AS7 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-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: ---------------------------------- Fix Version/s: Awaiting Volunteers > 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 > Labels: cdi, roadmap > 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-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: ---------------------------------- Fix Version/s: Awaiting Volunteers > 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 > Labels: roadmap > 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-687) Allow OSGi services to be registered as JAX-WS endpoints

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-687?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-687: ---------------------------------- Fix Version/s: Awaiting Volunteers > Allow OSGi services to be registered as JAX-WS endpoints > -------------------------------------------------------- > > Key: JBOSGI-687 > URL: https://issues.jboss.org/browse/JBOSGI-687 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi > Reporter: Thomas Diesler > Fix For: Awaiting Volunteers > > > It should be possible to register a WS endpoint similar to this > {code} > public void start(BundleContext context) { > HelloService helloService = new HelloServiceImpl(); > Dictionary props = new Hashtable(); > props.put("service.exported.interfaces", "*"); > props.put("service.exported.configs", "org.apache.cxf.ws"); > props.put("org.apache.cxf.ws.address", "http://localhost:8090/soap"); > registration = context.registerService(HelloService.class.getName(), helloService, props); > } > {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-689) Complete support for OSGi JNDI

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/JBOSGI-689?page=com.atlassian.jira.plugin... ] Thomas Diesler updated JBOSGI-689: ---------------------------------- Fix Version/s: Awaiting Volunteers > Complete support for OSGi JNDI > ------------------------------ > > Key: JBOSGI-689 > URL: https://issues.jboss.org/browse/JBOSGI-689 > Project: JBoss OSGi > Issue Type: Feature Request > Components: Enterprise OSGi, WildFly > Reporter: Thomas Diesler > Labels: jndi > Fix For: Awaiting Volunteers > > > As expected because of the missing integration with the NamingManger singletons, all tests that go through NamingManager to obtain the InitialContextFactory or the ObjectFactory fail. > {code} > Running org.jboss.test.osgi.example.jndi.JNDITestCase > Tests run: 12, Failures: 1, Errors: 2, Skipped: 2, Time elapsed: 15.574 sec <<< FAILURE! > Results : > Failed tests: testContextManagerReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): expected:<bar> but was:<Reference Class Name: java.lang.String(..) > Tests in error: > testTraditionalAPIValueBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader > testTraditionalAPIReferenceBinding(org.jboss.test.osgi.example.jndi.JNDITestCase): JBAS011843: Failed instantiate InitialContextFactory org.jboss.test.osgi.example.jndi.bundle.JNDITestActivator$SimpleInitalContextFactory from classloader ModuleClassLoader for Module "deployment.arquillian-service:main" from Service Module Loader > {code} > In reality it means that OSGi Bundles cannot use JNDI with object References and cannot expect the traditional JNDI API to work. These findings generally raise the question how a spec compliant OSGI JNDI Implementation is supposed to work in a container environment. Specifically, in an environment that has already set the NamingManager singletons. > IMHO there is a layer of abstraction missing. Perhaps the container should register a NamingManger service that the JNDI Implementation can use to register its InitialContextFactoryBuilder and ObjectFactoryBuilder. -- 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: ---------------------------------- Fix Version/s: Awaiting Volunteers > 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 > Labels: blueprint, roadmap > 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2013