Hi,
I have a part of my application that must run on OSGi. However I would like to enjoy the pleasures of WS stack, JPA, etc.
Let's say I package a JAR that contains
- WebService annotations
- OSGi Manifest entries + an activator class
I drop this jar in the /server/default/deploy dir of my JbossAS5 server.
1. How will my classes be loaded in memory: by OSGi or by the Jboss class loader ?
2. Will my WebService be deployed by JbossWS, and if yes, how will it have access to my classes if they have been deployed by OSGi ?
I am quite new to JBoss classloader and deployers. But from what I have understood, JBoss classloaded and OSGi classloader are incompatibles ? Is it possible to have a JAR inspected by several deployers (I don't know exactly how they work) ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4237058#4237058
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4237058
All
If I wanted to use log4j I have the following statement in my bundle manifest
<attribute name="Import-Package" value="org.osgi.framework;version=1.3.0,
org.apache.log4j,
And I have placed the log4j in the lib directory so it is in the classpath on startup. But my bundle still does not load it.
Caused by: java.lang.ClassNotFoundException: org.apache.commons.logging.LogFactory
Is there a set way to deploy thirdparty jars ?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4236822#4236822
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4236822
All
I have a bundle with the following manifest and I am trying to deploy it into a runtime jbossosgi
But when I deploy it I get the following error. I have the library on the classpath in runtime/lib for log4j
org.apache.felix.log.LogException: org.osgi.framework.BundleException: Unresolved constraint in bundle 13: package; (&(package=org.apache.log4j)(version>=1.2.15))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3097)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1439)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:779)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:760)
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235848#4235848
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235848
I am happy to announce the release of JBossOSGi-1.0.0.Beta2.
http://www.jboss.org/community/wiki/JBossOSGi100Beta2Released03-Jun-2009
You can download it here: https://sourceforge.net/project/downloading.php?group_id=22866&filename=j...
The release comes with improvements in the following areas
* JBoss OSGi Runtime has is now a pure OSGi container onto which components, services and applications can be deployed.
* Husky Test Framework for remote and embedded OSGi bundle testing
* Added support for JMX, JNDI services
* Microcontainer service to wire and configure OSGi components
For details please have a look at the latest version of our User Guide.
Here are the change log details
Feature Request
* [JBOSGI-70] - Expose bundle headers through JMX
Tasks
* [JBOSGI-79] - Provide POM descriptions for bundles
* [JBOSGI-86] - Document JBossOSGi Runtime
* [JBOSGI-88] - Document JMX Service
* [JBOSGI-89] - Document JNDI Service
* [JBOSGI-90] - Add hot-deployment to Runtime
Enjoy
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4235115#4235115
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4235115