Hi David, Am 01.09.2011 12:51, schrieb David Bosschaert:
http://team.ops4j.org/browse/PAXRUNNER-403
Ok, this is something we can work with - Pax projects should be able, in principle, to support all OSGi frameworks, and implementing another adapter for another framework is a rather well-defined task.
The discussion about whether or not JBoss AS is an OSGi framework is a bit pointless - if it were, then you could also call Eclipse, GlassFish or any other OSGi application an OSGi framework.
It wouldn't make sense for Pax projects to support every OSGi application in the world. Pax projects currently support the three major OSGi frameworks and provide APIs and SPIs for people to integrate their own OSGi applications with Pax.
Now, having narrowed the scope from JBoss AS to JBoss OSGi, I'm still curious about the use cases you have in mind - supporting JBoss OSGi in Pax Runner sounds a bit like a solution looking for a problem.
You don't need Pax Runner to start JBoss OSGi and provision bundles to it, JBoss OSGi has its own startup scripts and some kind of autodeploy folder or provisioning command, or both, I expect.
For testing OSGi bundles runnning on JBoss, you'd use Pax Exam rather than Pax Runner, and the Pax Exam Native Container in theory should work for JBoss OSGi without any changes from our side. (In practice it doesn't, due to that URL issue which is more likely to be on the JBoss side - I'll try to isolate a self-contained test case for you.)
Pax Exam 2.x more or less supersedes some parts of Pax Runner by new techniques of its own - once we better understand the question we might be able to provide better answers, and the answer might not be Pax Runner.
So what exactly are you looking for in Pax to support users of JBoss OSGi? Cheers, Harald _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
