On 10 apr. 2013, at 15:09, Cristiano Gavião wrote:
> Hi Peter,
> thanks for the time...
> maybe I'm wrong, but seems that going to PojoSR doesn't fill my main
> requirement: I need to run our API in JavaSE/EE and both Equinox (RCP
> applications) and Felix, too. I'm right?
So? The API for the services and the artifact formats are in all cases the
same. Sounds like a perfect solution to me?
Kind regards,
Peter Kriens
>
> best regards,
>
> Cristiano
>
> On 10/04/13 03:55, Peter Kriens wrote:
>> I PojoSR works very fine as an OSGi framework without classloaders. Amazing
>> as it sounds, most bundles work out of the box. It has a full blown service
>> registry and supports a surprising large number of OSGi concepts. What you
>> miss is on the fly installing/updating and uninstalling bundles. However,
>> activators, declarative services, it all works and services, like always,
>> can come and go.
>>
>> Since there is only one class loader, you find that all your J2EE code works
>> out of the box. I actually think this is a great way forward for many Java
>> users that want to use OSGi but have too many class loading hacks to make
>> the jump.
>>
>> It is based on the Apache Felix code base so the code is quite mature. It is
>> actively maintained by Karl Pauls.
>>
>> Kind regards,
>>
>> Peter Kriens
>>
>>
>> On 10 apr. 2013, at 05:52, Cristiano Gavião wrote:
>>
>>> Hello,
>>>
>>> I have a challenge and I would like some advice to figure out the best
>>> route to take.
>>>
>>> We have a framework api that currently runs in standard javaSE. Now I need
>>> to use that api in an OSGi environment (Equinox and Felix) but I still need
>>> be able to use it in javaSE (without any OSGi dependency).
>>>
>>> I started by turning the jars into bundles by using the maven-bundle-plugin
>>> to its maven modules.
>>>
>>> As expected, I'm facing some classloading exceptions due to the factories
>>> (with Class.forname(string)) that are being used inside the api. so I
>>> started to plan the movement to interfaces and services.
>>>
>>> But I'm a bit unsure what would be the best way to reproduce the OSGi
>>> service registration behavior in a javaSE environment, specially the
>>> initialization with the default implementation classes.
>>>
>>> Researching the web I could find two possibilities: java.util.ServiceLoader
>>> + http://aries.apache.org/modules/spi-fly.html and PojoSR. but not sure.
>>>
>>> please, could someone give me a light ?
>>>
>>> thank in advance,
>>>
>>> Cristiano
>>> _______________________________________________
>>> OSGi Developer Mail List
>>> [email protected]
>>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>>
>>
>>
>> _______________________________________________
>> OSGi Developer Mail List
>> [email protected]
>> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
> _______________________________________________
> OSGi Developer Mail List
> [email protected]
> https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
