[JBoss JIRA] Created: (JBOSGI-345) Support specifying start levels for bundles deployed in the deploy directory
by David Bosschaert (JIRA)
Support specifying start levels for bundles deployed in the deploy directory
----------------------------------------------------------------------------
Key: JBOSGI-345
URL: https://jira.jboss.org/browse/JBOSGI-345
Project: JBoss OSGi
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Core Framework
Affects Versions: JBossOSGi 1.0.0 Beta7
Reporter: David Bosschaert
Assignee: David Bosschaert
When deloying bundles by placing them in the deploy directory it should be possible to specify their start level and whether they need to be started or just installed.
One idea is to start supporting 'companion' files that have the same name as the bundle but then with a different extension. So information like this could be placed in a myBundle.md file for a bundle called myBundle.jar. The .md file would be placed in the deploy directory as well and needs to be there before the bundle.
Another note is that this mechanism should also work when JBosgi is run in AS
--
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
12 years, 9 months
[JBoss JIRA] Created: (JBOSGI-309) OSGi Runtime fails on cygwin
by Thomas Diesler (JIRA)
OSGi Runtime fails on cygwin
----------------------------
Key: JBOSGI-309
URL: https://jira.jboss.org/jira/browse/JBOSGI-309
Project: JBoss OSGi
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Productization
Reporter: Thomas Diesler
Fix For: JBossOSGi 1.0.x
$ bin/run.sh
=========================================================================
JBossOSGi Bootstrap Environment
OSGI_HOME: C:\jboss\jboss-osgi-1.0.0.Beta6-MC\runtime
JAVA: /cygdrive/c/jdk1.6.0_18/bin/java
JAVA_OPTS: -Dprogram.name=run.sh -Dosgi.home=/cygdrive/c/jboss/jboss-osgi-1.0.
0.Beta6-MC/runtime -server -Xms128m -Xmx512m -XX:MaxPermSize=256m -Dsun.rmi.dgc.
client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000
=========================================================================
log4j:WARN No appenders could be found for logger (org.jboss.osgi.spi.internal.O
SGiBootstrapBean).
log4j:WARN Please initialize the log4j system properly.
Exception in thread "main" java.lang.IllegalStateException: Cannot find any boot
strap: [[jboss-osgi-bootstrap.xml, bootstrap/jboss-osgi-bootstrap.xml, META-INF/
jboss-osgi-bootstrap.xml, META-INF/jboss-osgi-default-bootstrap.xml]]
at org.jboss.osgi.framework.launch.OSGiFrameworkFactory.newFramework(OSG
iFrameworkFactory.java:115)
at org.jboss.osgi.spi.framework.PropertiesBootstrapProvider.createFramew
ork(PropertiesBootstrapProvider.java:239)
at org.jboss.osgi.spi.framework.PropertiesBootstrapProvider.initFramewor
kInstance(PropertiesBootstrapProvider.java:166)
at org.jboss.osgi.spi.framework.PropertiesBootstrapProvider.configureInt
ernal(PropertiesBootstrapProvider.java:160)
at org.jboss.osgi.spi.framework.PropertiesBootstrapProvider.getFramework
(PropertiesBootstrapProvider.java:294)
at org.jboss.osgi.spi.internal.OSGiBootstrapBean.run(OSGiBootstrapBean.j
ava:78)
at org.jboss.osgi.spi.framework.OSGiBootstrap.main(OSGiBootstrap.java:57
)
--
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, 9 months
[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, 9 months
[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, 9 months