August 2009 - jboss-osgi-issues - Jboss List Archives

[JBoss JIRA] Created: (JBOSGI-81) Provide propper JNDI integration (RFP-84)

by Thomas Diesler (JIRA)

Provide propper JNDI integration (RFP-84) ----------------------------------------- Key: JBOSGI-81 URL: https://jira.jboss.org/jira/browse/JBOSGI-81 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: Thomas Diesler https://www.osgi.org/members/svn/documents/trunk/rfps/rfp-0084-JNDI-Integ... -- 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

11 years, 9 months

4
52
0 / 0

[JBoss JIRA] Created: (JBOSGI-72) Setup a bundle repository

by Thomas Diesler (JIRA)

Setup a bundle repository ------------------------- Key: JBOSGI-72 URL: https://jira.jboss.org/jira/browse/JBOSGI-72 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta2 -- 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

11 years, 11 months

1
5
0 / 0

[JBoss JIRA] Created: (JBOSGI-62) Distributed OSGi Example

by Thomas Diesler (JIRA)

Distributed OSGi Example ------------------------ Key: JBOSGI-62 URL: https://jira.jboss.org/jira/browse/JBOSGI-62 Project: JBossOSGi Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x -- 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

12 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-58) Framework injection in SLSB

by Thomas Diesler (JIRA)

Framework injection in SLSB --------------------------- Key: JBOSGI-58 URL: https://jira.jboss.org/jira/browse/JBOSGI-58 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Framework Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta1 I'm tring to access the OSGIFramework from my Stateless and I got this error: Caused by: javax.management.InstanceNotFoundException: jboss.osgi:service=Framework is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:529) at org.jboss.mx.server.MBeanServerImpl.getMBeanInfo(MBeanServerImpl.java:675) at org.jboss.mx.util.MBeanProxyExt.init(MBeanProxyExt.java:407) at org.jboss.mx.util.MBeanProxyExt.(MBeanProxyExt.java:99) at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:394) at org.jboss.mx.util.MBeanProxyExt.create(MBeanProxyExt.java:349) at org.jboss.injection.DependsFieldInjector.inject(DependsFieldInjector.java:66) @Stateless public class TestStatelessBean implements TestStatelessRemote { @Depends("jboss.osgi:service=Framework") OSGiFramework framework; @Override public void test() throws NamingException { System.out.println(framework.getSystemBundle()); } -- 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

12 years, 8 months

1
6
0 / 0

[JBoss JIRA] Created: (JBOSGI-82) Remove the requirement to set the context classloader for JNDI access

by Thomas Diesler (JIRA)

Remove the requirement to set the context classloader for JNDI access --------------------------------------------------------------------- Key: JBOSGI-82 URL: https://jira.jboss.org/jira/browse/JBOSGI-82 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: 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

12 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBOSGI-55) Write an RHQ plugin for managing JBoss OSGi

by Thomas Diesler (JIRA)

Write an RHQ plugin for managing JBoss OSGi ------------------------------------------- Key: JBOSGI-55 URL: https://jira.jboss.org/jira/browse/JBOSGI-55 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Productization Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.x Ian Springer says: I think it would be great if we could write an RHQ plugin for managing JBoss OSGi. That would allow it to be managed using EmbJopr (i.e. an admin console webapp like the Felix one you have today) or Jopr/JON. Not only would we be eating our own dog food, but I think we'd end up with something a lot nicer than Felix with not a ton of work required. Please ping me or one of the other developers on the JON team if you'd like to discuss this some more. We'd be glad to help you get started writing a plugin. -- 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

12 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBOSGI-75) Implements URLStreamHandlerService

by Thomas Diesler (JIRA)

Implements URLStreamHandlerService ---------------------------------- Key: JBOSGI-75 URL: https://jira.jboss.org/jira/browse/JBOSGI-75 Project: JBossOSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Thomas Diesler Through the URLStreamHandlerService bundles can provide their own URL stream and content handlers http://www.osgi.org/javadoc/r4v41/org/osgi/service/url/URLStreamHandlerSe... Use this instead of setting the sysprop java.protocol.handler.pkgs=org.jboss.net.protocol|org.jboss.virtual.protocol Felix-1.6.0 defaults to private static final String DEFAULT_STREAM_HANDLER_PACKAGE = "sun.net.www.protocol|com.ibm.oti.net.www.protocol|gnu.java.net.protocol|wonka.net|com.acunia.wonka.net|org.apache.harmony.luni.internal.net.www.protocol|weblogic.utils|weblogic.net|javax.net.ssl|COM.newmonics.www.protocols"; -- 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

13 years

2
9
0 / 0

[JBoss JIRA] Created: (JBOSGI-105) Investigate lazy bundle activation for runtime bundles

by Thomas Diesler (JIRA)

Investigate lazy bundle activation for runtime bundles ------------------------------------------------------ Key: JBOSGI-105 URL: https://jira.jboss.org/jira/browse/JBOSGI-105 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Components: Runtime Reporter: Thomas Diesler Fix For: JBossOSGi 1.0.0 Beta3 OSGi has a build-in notion of lazy bundle activation - which I have not (yet) looked into. In theory this should bring startup time very close to boot time. i.e. the 'all' profile might start in < 1sec If this is true we can put the web console into the 'default' profile without negatively effecting the startup time. -- 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

13 years

1
15
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

13 years, 9 months

2
15
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

13 years, 9 months

1
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-issues August 2009