On 06/05/2013 03:00 AM, Thomas Diesler wrote:
Hi Brett,
The primary target for the Arquillian OSGi Container
<https://github.com/arquillian/arquillian-container-osgi> is our own
OSGi Framework <https://github.com/jbosgi/jbosgi-framework>, which is a
compliant R5 implementation. This also explains why I removed support
for Felix because it is not (yet) R5 compliant AFAIK. Theoretically, it
would probably be possible to change pom such that it uses an older
version of the OSGi APIs when running with Felix.
To be a good (corporate) citizen you run and talk about hibernate on the
jbosgi framework. Do you have a specific reason not to?
I thought this is what people are already doing when they use the Hibernate ORM on jbosgi (since Hibernate ORM is a component). I think the Hibernate team is already contributing quite a bit and I see no reason to accuse (insulting) them of not being good citizens of the world.
Scott, this was not intended to be an insult not even a criticism. If it came across like it, I'm really sorry - perhaps you can blame it on poor german -> english translation.
For standalone use though, what is the model for getting the jbosgi framework as a single (maven artifact) component? I'm asking this for my own information (not related to Hibernate native OSGi container support which I think is what Brett is talking about). I have heard talk about *embedded* (framework/platform) support in the past but not sure if we have anything to show yet.
The primary target of the jbosgi framework is wildly. There is only a single reason for jboss to even get into the core framework business, which is provide OSGi functionality in the AppServer. Specifically, the framework has been designed such that it can integrate with all other modules that also run in WildFly. The goal is to allow access to OSGi services from JavaEE components and vice versa. The upcomming 8.0.0.Alpha2 release will be the first container (for over a year) that we can actually base a jbosgi release on, which then contains updated R5 documentation, examples, binaries etc.
The R5 OSGi TCK runs on a single aggregated binary that is
distributed through maven. Having said that, we don't target the standalone OSGi Framework market and our framework. Nevertheless, it should behave like any other R5 compliant framework and I'd be interested to see if hibernate+aries-jpa can actually run on it successfully. Hopefully this answers your question. If not, please ping on skype or any other channel and we can talk more.