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

[JBoss JIRA] Created: (JBOSGI-360) Integrate jbosgi-container into jbosgi umbrella

by Thomas Diesler (JIRA)

Integrate jbosgi-container into jbosgi umbrella ----------------------------------------------- Key: JBOSGI-360 URL: https://jira.jboss.org/browse/JBOSGI-360 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler #1 Integrate jbosgi-container in the build and hudson setup (partly done) #2 make it the default framework - when the majority of tests pass #3 replace core framework in the installer - criteria is that enterprise examples pass embedded and remote -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-203) Define non OSGi bundle handling by the Framework

by Thomas Diesler (JIRA)

Define non OSGi bundle handling by the Framework ------------------------------------------------ Key: JBOSGI-203 URL: https://jira.jboss.org/jira/browse/JBOSGI-203 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta5 There have been changes going forth and back with respect to non-osgi deployment handling. The objectives and scope of functionality need to be defined. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-329) SystemBundle added as MC module

by Thomas Diesler (JIRA)

SystemBundle added as MC module ------------------------------- Key: JBOSGI-329 URL: https://jira.jboss.org/browse/JBOSGI-329 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Currently we do not create OSGiPackageRequirements that map to system packages defined at the framework level. In various places, especially in resolver integration, that leads to special workaround treatment when a bundle defines a requirement on a system package (possibly with a version qualifier) -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-141) Service integration with MC

by Thomas Diesler (JIRA)

Service integration with MC --------------------------- Key: JBOSGI-141 URL: https://jira.jboss.org/jira/browse/JBOSGI-141 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Reporter: Thomas Diesler Fix For: Framework 1.0.x and vice versa. * Service --> MC The service layer is not so well integrated with the MC. It does just enough to be "OSGi compliant" (of course that's not yet tested). So this is at the moment very simple. The OSGiServiceState which should eventually turn into an MC context implementation has two "facades", the standard ServiceRegistration and ServiceReference interfaces. * MC --> Service Services are also largely complete. What's missing is that we want to expose MC pojos and JMX MBeans etc. as OSGi services. The proper way to do this would be to push the OSGi Filter into kernel project and use the MDR INSTANCE scope as the attributes. There would be a gotcha in that OSGi expect attributes to have case insensitive names, but we would only have to enforce that for OSGi created services. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
15
0 / 0

[JBoss JIRA] Created: (JBOSGI-337) Document usage of the urn:jboss:pojo2osgi:1.0 namespace

by Thomas Diesler (JIRA)

Document usage of the urn:jboss:pojo2osgi:1.0 namespace ------------------------------------------------------- Key: JBOSGI-337 URL: https://jira.jboss.org/browse/JBOSGI-337 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Ales Justin Fix For: JBossOSGi 1.0.0 Beta8 -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-330) Invalid capability matching for dynamic or optional imports

by Thomas Diesler (JIRA)

Invalid capability matching for dynamic or optional imports ----------------------------------------------------------- Key: JBOSGI-330 URL: https://jira.jboss.org/browse/JBOSGI-330 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta8 The OSGiPackageCapability requires a workaround in resolve that falls back to simple package name, version and attribute matching if (osgiRequirement.isDynamic() || osgiRequirement.isOptional()) { match = super.resolves(reqModule, mcRequirement); match &= matchAttributes(osgiRequirement); } -- 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

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBOSGI-205) Document MC/OSGi Service integration

by Thomas Diesler (JIRA)

Document MC/OSGi Service integration ------------------------------------ Key: JBOSGI-205 URL: https://jira.jboss.org/jira/browse/JBOSGI-205 Project: JBoss OSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Assignee: Ales Justin Please create a section in the user guide that explains what added benefit this MC/OSGi Service integration brings to the user. If applicable, there should be examples that the user can run and look at. This integration work is the first piece of functionality that we do to justify our effort to implement an OSGi core framework, hence special care should be taken to explain and show the actual benefits. * OSGi services will be exposed as MC beans I suppose that means you can reference/inject OSGi services in the an MC descriptor. Could you describe/show how this would look like? How would this work with service properties. How would this work with multiple implementations of the same service interface? * MC beans will be listed as a OSGi services I suppose that means you can reference/inject MC beans in a BP descriptor. Here as well, could you please describe/show how this would look like? Do MC beans support service properties i.e. Can I use an LDAP filter to find the target service? Can you have multiple implementations of the same service interface? How would the service event model work i.e. Can I use ServiceTracker to track MC beans? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-76) Add VFS to microcontainer bundle

by Thomas Diesler (JIRA)

Add VFS to microcontainer bundle -------------------------------- Key: JBOSGI-76 URL: https://jira.jboss.org/jira/browse/JBOSGI-76 Project: JBossOSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Thomas Diesler -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-358) Uninstall of updated bundle fails

by Thomas Diesler (JIRA)

Uninstall of updated bundle fails --------------------------------- Key: JBOSGI-358 URL: https://jira.jboss.org/browse/JBOSGI-358 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: Core Framework Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 java.lang.IllegalStateException: Bundle already uninstalled: Bundle{update-bundle1-1.0.0} at org.jboss.osgi.framework.bundle.DeployedBundleState.uninstall(DeployedBundleState.java:261) at org.jboss.osgi.framework.bundle.OSGiBundleWrapper.uninstall(OSGiBundleWrapper.java:196) at org.jboss.test.osgi.bundle.BundleTestCase.testUpdate(BundleTestCase.java:191) -- 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

15 years, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-367) JTA activator cannot find DocumentBuilderFactory

by Thomas Diesler (JIRA)

JTA activator cannot find DocumentBuilderFactory ------------------------------------------------ Key: JBOSGI-367 URL: https://jira.jboss.org/browse/JBOSGI-367 Project: JBoss OSGi Issue Type: Bug Security Level: Public (Everyone can see) Components: jboss-osgi-jta Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta9 Caused by: javax.xml.parsers.FactoryConfigurationError: Provider org.jboss.osgi.xml.DocumentBuilderFactoryImpl not found at javax.xml.parsers.DocumentBuilderFactory.newInstance(DocumentBuilderFactory.java:129) at com.arjuna.common.internal.util.propertyservice.plugins.io.XMLFilePlugin.<clinit>(XMLFilePlugin.java:352) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at com.arjuna.common.internal.util.propertyservice.PropertyManagerImpl.load(PropertyManagerImpl.java:357) at com.arjuna.ats.jta.common.jtaPropertyManager.<clinit>(jtaPropertyManager.java:67) at com.arjuna.ats.jta.utils.JNDIManager.getTransactionManagerImplementationClassname(JNDIManager.java:72) at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:93) at com.arjuna.ats.jta.TransactionManager.transactionManager(TransactionManager.java:76) at org.jboss.osgi.jta.internal.TransactionServiceActivator.start(TransactionServiceActivator.java:61) -- 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

15 years, 3 months

1
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues July 2010