jboss-osgi-users December 2009

jboss-osgi-users@lists.jboss.org

1 participants
4 discussions

[JBoss OSGi Users] - JBossOSGi 1.0.0.Beta5 Released (09-Dec-2009)

by thomas.diesler＠jboss.com

I am happy to announce the release of JBossOSGi-1.0.0.Beta5. http://jbossosgi.blogspot.com/2009/12/jbossosgi-100beta5-released.html The release comes with improvements in the following areas * Improved JBoss Microcontainer based Framework support. * Improved Eclipse Equinox Integration support. * Added Enterprise OSGi Transaction support. * Added Compendium Event Admin support. * Added JBossXB based XML Binding support. * Added Lifecycle Interceptor support. For details please have a look at the latest version of our User Guide. Here are the change log details Bug * [JBOSGI-129] - Filter behaviour change in r4v42 * [JBOSGI-137] - Cannot parse Bundle-SymbolicName * [JBOSGI-153] - Cannot parse Import-Package parameters * [JBOSGI-187] - Husky SocketInvocation may block forever * [JBOSGI-199] - Use thread safe collections where information is mutable * [JBOSGI-212] - Cannot refresh Microcontainer service Feature Request * [JBOSGI-125] - Add ManagedFramework service * [JBOSGI-202] - Allow override of where the bootstrap file comes from Task * [JBOSGI-157] - JTA (RFC-98) - Initial Implementation * [JBOSGI-181] - Add EventAdmin as available service * [JBOSGI-182] - Release JBoss OSGi 1.0.0.Beta5 * [JBOSGI-183] - Introduce notion of OSGi Interceptors * [JBOSGI-188] - Separate DeployerService from SPI * [JBOSGI-190] - Allign getting started guide with latest release * [JBOSGI-200] - Split getParameter(s) calls into directives/attributes * [JBOSGI-215] - Update Blueprint to 1.0.0.Alpha3 * [JBOSGI-216] - Update to Apache Felix-2.0.2 * [JBOSGI-217] - Update to Eclipse Equinox-3.5.1 * [JBOSGI-218] - Update to jboss-osgi-common-1.0.3 * [JBOSGI-219] - Update to jboss-osgi-husky-1.0.2 * [JBOSGI-220] - Update to jboss-osgi-jmx-1.0.2 * [JBOSGI-221] - Update to jboss-osgi-jndi-1.0.2 * [JBOSGI-222] - Update to jboss-osgi-microcontainer-2.0.9 * [JBOSGI-223] - Update to jboss-osgi-spi-1.0.3 * [JBOSGI-224] - Update to jboss-osgi-xml-binding-2.0.2.Beta3 * [JBOSGI-225] - Update to jboss-osgi-apache-xerces-2.9.1.SP3 * [JBOSGI-226] - Update to jboss-osgi-hotdeploy-1.0.3 * [JBOSGI-227] - Update to jboss-osgi-framework-1.0.0.Alpha2 * [JBOSGI-228] - Update to jboss-osgi-jaxb-2.1.10.SP3 * [JBOSGI-229] - Add jboss-osgi-deployment-1.0.0 * [JBOSGI-230] - Add jboss-osgi-jta-1.0.0 * [JBOSGI-231] - Add jboss-osgi-reflect-2.0.2 * [JBOSGI-232] - Add jboss-osgi-webapp-0.7.2 * [JBOSGI-233] - Update to org.apache.felix.configadmin-1.2.4 * [JBOSGI-234] - Add org.apache.felix.eventadmin-1.0.0 Enjoy View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269763#4269763 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269763

14 years, 4 months

1
0
0 / 0

[JBoss OSGi Users] - Re: Access OSGIFramework from Stateless

by thomas.diesler＠jboss.com

| @Remote | @Stateless(name="StatelessBean") | public class StatelessBeanImpl implements StatelessBean | { | @Depends("jboss.osgi:service=ManagedFramework") | ManagedFrameworkMBean framework; | | public String getFraemworkSymbolicName() | { | ObjectName bundle = framework.getBundle(0); | return bundle.getKeyProperty(ManagedBundle.PROPERTY_SYMBOLIC_NAME); | } | } | which currently fails with | 17:56:53,548 INFO [MainDeployer] deploy, url=file:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/functional/target/test-libs/jbosgi58-ejb.jar | 17:56:53,952 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@22494867{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/functional/target/test-libs/jbosgi58-ejb.jar/} | 17:56:53,953 INFO [Ejb3DependenciesDeployer] Encountered deployment AbstractVFSDeploymentContext@22494867{vfszip:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/functional/target/test-libs/jbosgi58-ejb.jar/} | 17:56:53,982 WARN [InterceptorInfoRepository] EJBTHREE-1852: InterceptorInfoRepository is deprecated | 17:56:54,892 INFO [JBossASKernel] Created KernelDeployment for: jbosgi58-ejb.jar | 17:56:54,900 INFO [JBossASKernel] installing bean: jboss.j2ee:jar=jbosgi58-ejb.jar,name=StatelessBean,service=EJB3 | 17:56:54,901 INFO [JBossASKernel] with dependencies: | 17:56:54,901 INFO [JBossASKernel] and demands: | 17:56:54,901 INFO [JBossASKernel] jboss.osgi:service=ManagedFramework | 17:56:54,901 INFO [JBossASKernel] jboss.ejb:service=EJBTimerService | 17:56:54,901 INFO [JBossASKernel] and supplies: | 17:56:54,902 INFO [JBossASKernel] jndi:StatelessBean/remote | 17:56:54,902 INFO [JBossASKernel] Class:org.jboss.test.osgi.jbossas.jbosgi58.ejb.StatelessBean | 17:56:54,902 INFO [JBossASKernel] jndi:StatelessBean/remote-org.jboss.test.osgi.jbossas.jbosgi58.ejb.StatelessBean | 17:56:54,902 INFO [JBossASKernel] Added bean(jboss.j2ee:jar=jbosgi58-ejb.jar,name=StatelessBean,service=EJB3) to KernelDeployment of: jbosgi58-ejb.jar | 17:56:55,251 WARN [MainDeployer] Failed to deploy: file:/home/tdiesler/svn/jboss-osgi/trunk/testsuite/functional/target/test-libs/jbosgi58-ejb.jar | org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS): | | DEPLOYMENTS MISSING DEPENDENCIES: | Deployment "jboss.j2ee:jar=jbosgi58-ejb.jar,name=StatelessBean,service=EJB3" is missing the following dependencies: | Dependency "<UNKNOWN jboss.j2ee:jar=jbosgi58-ejb.jar,name=StatelessBean,service=EJB3>" (should be in state "Installed", but is actually in state "** UNRESOLVED Demands 'jboss.osgi:service=ManagedFramework' **") | Deployment "jboss.j2ee:jar=jbosgi58-ejb.jar,name=StatelessBean,service=EJB3_endpoint" is missing the following dependencies: | Dependency "jboss.j2ee:jar=jbosgi58-ejb.jar,name=StatelessBean,service=EJB3" (should be in state "Installed", but is actually in state "PreInstall") | | DEPLOYMENTS IN ERROR: | Deployment "<UNKNOWN jboss.j2ee:jar=jbosgi58-ejb.jar,name=StatelessBean,service=EJB3>" is in error due to the following reason(s): ** UNRESOLVED Demands 'jboss.osgi:service=ManagedFramework' ** | | at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1002) | at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:948) | at org.jboss.osgi.framework.deployers.OSGiDeployersWrapper.checkComplete(OSGiDeployersWrapper.java:182) | at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870) | at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:859) | View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269398#4269398 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269398

14 years, 4 months

1
0
0 / 0

[JBoss OSGi Users] - Re: Installing and running bundles on Jboss

by thomas.diesler＠jboss.com

The framework integration in JBossAS is preconfigured. I assume that this code does *not* create a new instance of an OSGi Framework in JBoss. If it does it would be incorrect. | FrameworkIntegration inte = new FrameworkIntegration(); | inte.create(); | Instead the Framework should be injected as an MC bean or accessed via JMX. anonymous wrote : | This experiment works on Felix, but on Equinox i get null pointers when I try to get the context and other. Why? | The Equinox integration in Beta4 and earlier is poor. With Beta5 (which should come out this week) you should have a mucch better experience. Try running the provided examples with the Equinox on the target container of your choice. If you can't wait for the release, you can work from trunk, only the user documentation is still in flux. anonymous wrote : | Did I start another Felix container | Yes, you probably started a new FW instance. The user guide should tell you the MC bean names http://jbmuc.dyndns.org/jboss-osgi/userguide/html/ChapFrameworkIntegratio... View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269338#4269338 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269338

14 years, 4 months

1
0
0 / 0

[JBoss OSGi Users] - Installing and running bundles on Jboss

by PedroGomes

I'm currently working on a project for a application deployed in Jboss where we can deploy bundles to implement a new functionality. After some tests with with Felix and Equinox, I created a little EJB application that installs and runs bundles using some actions offered by them. | public String doInstall() { | | FrameworkIntegration inte = new FrameworkIntegration(); | inte.create(); | //inte.start(); | context = inte.getBundleContext(); | try{ | context.installBundle("file:///Users/ped/Desktop/UCE15/PluginJars/libPlugin.jar"); | context.installBundle("file:///Users/ped/Desktop/UCE15/PluginJars/sensorPlugin.jar"); | ... | }catch.... | | } | | | public String doAction() { | | if(context==null){ | FrameworkIntegration inte = new FrameworkIntegration(); | inte.create(); | inte.start(); | context = inte.getBundleContext(); | } | | Bundle[] bds = context.getBundles(); | for(Bundle b : bds){ | System.out.println("BundleID: "+b.getBundleId()+ " Name: " + b.getSymbolicName() +" State: "); | try { | b.start(); | } catch (BundleException e) { | System.out.println("Exception on bundle start: "+e.getCause().toString()); | } | } | return "Run"; | } | Now, the questions: 1) This experiment works on Felix, but on Equinox i get null pointers when I try to get the context and other. Why? 2) When running on Felix, I can install and run the plugins, but i don't see the bundles installed by Jboss on start, the same ones I see on the configuration page for bundles. And vice-versa, i don't see my bundles on the page. Did I start another Felix container (or something like that, I'm not a pro on OSGi sry)?. And can I get the Jboss container so I can see my bundles on the page, and install new ones from there? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4269147#4269147 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4269147

14 years, 4 months

1
0
0 / 0

← Newer
1
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

jboss-osgi-users December 2009