You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@deltaspike.apache.org by Charles Moulliard <ch...@gmail.com> on 2012/09/04 09:51:13 UTC
Re: OSGi support
Hi Harald,
I have added OSGI support for DeltaSpike Core, Impl and JPA modules and
deployed them successfully on Karaf. Can you make some tests please ?
https://issues.apache.org/jira/browse/DELTASPIKE-210
Regards,
Charles
On Tue, Sep 4, 2012 at 8:58 AM, Charles Moulliard <ch...@gmail.com> wrote:
> Hi Harald,
>
> What is your IRC account ? I'm currently working on Deltaspike to add OSGI
> support. Could be interesting that you make some tests if you agree ?
>
> Regards,
>
> Charles
>
>
> On Fri, Aug 31, 2012 at 5:41 PM, Charles Moulliard <ch...@gmail.com>wrote:
>
>> FYI
>>
>>
>> ---------- Forwarded message ----------
>> From: Charles Moulliard <ch...@gmail.com>
>> Date: Fri, Aug 31, 2012 at 5:15 PM
>> Subject: Re: OSGi support
>> To: deltaspike-users@incubator.apache.org
>>
>>
>> Hi Harald,
>>
>> Many thanks to share this information and to collaborate with us about
>> what you plan to do with PAX CDI project. I will have a look about adding
>> bundle support for our maven modules beginning of next week. I will keep
>> you informed through the ticket regarding this and also git-svn exchange.
>>
>> Regards,
>>
>> Charles
>>
>>
>> On Fri, Aug 31, 2012 at 5:07 PM, Harald Wellmann <hw...@gmail.com>wrote:
>>
>>> At OPS4J, there is a new project Pax CDI [1] for integrating CDI with
>>> OSGi. In this project, I'm currently working on declarative
>>> transactions using Deltaspike JPA in combination with Pax JPA and Pax
>>> JDBC which means that we'll require OSGi bundles of Deltaspike Core
>>> and JPA modules rather sooner than later.
>>>
>>> I raised a corresponding feature request [2] about two months ago,
>>> which is still unchanged, so I wonder if OSGi is on the agenda for
>>> Deltaspike at all?
>>>
>>> At the moment, I'm using a local clone of the GitHub DeltaSpike
>>> mirror, which I'm ready to push to GitHub. I don't really know any
>>> details about the ASF Subversion to GitHub connection, so if there's a
>>> better way of sharing changes and potentially having them pulled by
>>> Deltaspike, please let me know.
>>>
>>> [1] http://team.ops4j.org/wiki/display/PAXCDI
>>> [2] https://issues.apache.org/jira/browse/DELTASPIKE-210
>>>
>>> Best regards,
>>> Harald
>>>
>>
>>
>>
>> --
>> Charles Moulliard
>> Apache Committer / Sr. Pr. Consultant at FuseSource.com
>> Twitter : @cmoulliard
>> Blog : http://cmoulliard.blogspot.com
>>
>>
>>
>>
>>
>> --
>> Charles Moulliard
>> Apache Committer / Sr. Pr. Consultant at FuseSource.com
>> Twitter : @cmoulliard
>> Blog : http://cmoulliard.blogspot.com
>>
>>
>>
>
>
> --
> Charles Moulliard
> Apache Committer / Sr. Pr. Consultant at FuseSource.com
> Twitter : @cmoulliard
> Blog : http://cmoulliard.blogspot.com
>
>
>
--
Charles Moulliard
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Twitter : @cmoulliard
Blog : http://cmoulliard.blogspot.com
Re: OSGi support
Posted by Harald Wellmann <hw...@gmail.com>.
Thanks a lot, we're almost there... There's just another package import
that maven-bundle-plugin doesn't recognize automatically.
See my comment in https://issues.apache.org/jira/browse/DELTASPIKE-210
By the way, do you deploy your snapshots to a public Maven repository?
If so, I could drop the DeltaSpike job on OPS4J Hudson and grab the
0.4-incubation-SNAPSHOTs from there.
Best regards,
Harald
Am 05.09.2012 08:35, schrieb Charles Moulliard:
> Modification done Harald
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-deltaspike.git;a=commit;h=1877ca06094408113c57b518ece125d72008a94e
>
Re: OSGi support
Posted by Charles Moulliard <ch...@gmail.com>.
Modification done Harald
https://git-wip-us.apache.org/repos/asf?p=incubator-deltaspike.git;a=commit;h=1877ca06094408113c57b518ece125d72008a94e
On Tue, Sep 4, 2012 at 2:42 PM, Harald Wellmann <hw...@gmail.com>wrote:
> That would be very helpful indeed!
>
> Thanks
> Harald
>
> 2012/9/4 Charles Moulliard <ch...@gmail.com>:
> > I can add this option in the header till it becomes a standard
> >
>
--
Charles Moulliard
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Twitter : @cmoulliard
Blog : http://cmoulliard.blogspot.com
Re: OSGi support
Posted by Harald Wellmann <hw...@gmail.com>.
That would be very helpful indeed!
Thanks
Harald
2012/9/4 Charles Moulliard <ch...@gmail.com>:
> I can add this option in the header till it becomes a standard
>
Re: OSGi support
Posted by Charles Moulliard <ch...@gmail.com>.
I can add this option in the header till it becomes a standard
On Tue, Sep 4, 2012 at 12:35 PM, Harald Wellmann <hw...@gmail.com>wrote:
> 2012/9/4 Charles Moulliard <ch...@gmail.com>:
> > Hi Harald,
> >
> > I would prefer that we adopt an OSGI name convention for that feature and
> > not something specific to Pax.
>
> Yes sure, it's just a chicken-and-egg problem, as there is no standard
> yet and Pax CDI attempts to provide input for the standard...
>
> Best regards,
> Harald
>
--
Charles Moulliard
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Twitter : @cmoulliard
Blog : http://cmoulliard.blogspot.com
Re: OSGi support
Posted by Harald Wellmann <hw...@gmail.com>.
2012/9/4 Charles Moulliard <ch...@gmail.com>:
> Hi Harald,
>
> I would prefer that we adopt an OSGI name convention for that feature and
> not something specific to Pax.
Yes sure, it's just a chicken-and-egg problem, as there is no standard
yet and Pax CDI attempts to provide input for the standard...
Best regards,
Harald
Re: OSGi support
Posted by Charles Moulliard <ch...@gmail.com>.
Hi Harald,
I would prefer that we adopt an OSGI name convention for that feature and
not something specific to Pax.
Regards,
Charles
On Tue, Sep 4, 2012 at 11:03 AM, Harald Wellmann <hw...@gmail.com>wrote:
> Hi Charles,
>
> thanks a lot, I'll try that with Pax CDI. This will require some
> preparation, though...
>
> The point is that the OSGi CDI RFP requires an opt-in mechanism for
> CDI-enabled bundles, and I'm currently using a specific manifest
> header
>
> Pax-ManagedBeans: META-INF/beans.xml
>
> Bundles without that header will not be picked up by the CDI extender,
> even if they contain a beans.xml resource.
>
> So testing would be trivial if these headers were present, otherwise
> I'll have to implement a way to opt out of opt-in ;-).
>
> Would it be an option for DeltaSpike to include this preliminary
> header, until the OSGi Alliance has specified the details of the
> opt-in mechanism?
>
> Best regards,
> Harald
>
>
> 2012/9/4 Charles Moulliard <ch...@gmail.com>:
> > Hi Harald,
> >
> > I have added OSGI support for DeltaSpike Core, Impl and JPA modules and
> > deployed them successfully on Karaf. Can you make some tests please ?
> >
> > https://issues.apache.org/jira/browse/DELTASPIKE-210
> >
>
--
Charles Moulliard
Apache Committer / Sr. Pr. Consultant at FuseSource.com
Twitter : @cmoulliard
Blog : http://cmoulliard.blogspot.com
Re: OSGi support
Posted by Harald Wellmann <hw...@gmail.com>.
Hi Charles,
thanks a lot, I'll try that with Pax CDI. This will require some
preparation, though...
The point is that the OSGi CDI RFP requires an opt-in mechanism for
CDI-enabled bundles, and I'm currently using a specific manifest
header
Pax-ManagedBeans: META-INF/beans.xml
Bundles without that header will not be picked up by the CDI extender,
even if they contain a beans.xml resource.
So testing would be trivial if these headers were present, otherwise
I'll have to implement a way to opt out of opt-in ;-).
Would it be an option for DeltaSpike to include this preliminary
header, until the OSGi Alliance has specified the details of the
opt-in mechanism?
Best regards,
Harald
2012/9/4 Charles Moulliard <ch...@gmail.com>:
> Hi Harald,
>
> I have added OSGI support for DeltaSpike Core, Impl and JPA modules and
> deployed them successfully on Karaf. Can you make some tests please ?
>
> https://issues.apache.org/jira/browse/DELTASPIKE-210
>