cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eoghan Glynn <>
Subject Fwd: [VOTE] Release CXF dOSGi 1.0
Date Tue, 05 May 2009 09:43:22 GMT
Sent this earlier to dkulp individually, I meant to reply-all.

---------- Forwarded message ----------
From: Eoghan Glynn <>
Date: 2009/5/5 10:13
Subject: Re: [VOTE] Release CXF dOSGi 1.0
To: Daniel Kulp <>

2009/5/4 Daniel Kulp <>:
> On Mon May 4 2009 5:30:49 pm Eoghan Glynn wrote:
>> On issue #4, I'm of a mind to just pull in the samples bundles
>> directly in from maven. This is especially convenient when using the
>> Pax URL mvn protocol, allowing a mvn:groupId:artifactId:version style
>> of URL to referenced directly from the OSGi shell. This would be the
>> most natural approach for SMX4 in any case (BTW I'm planning to wrap
>> dOSGi up as a couple of SMX4 features, which would add another layer
>> of convenience).
> Well, part of the purpose of a "sample" is to provide the CODE for the sample
> so they can see how it works, modify it, learn from it, etc... Pulling the
> existing stuff from maven kind of defeats that purpose, does it not?

Well no, I wouldn't say it defeats the purpose. The demo is described
in a very detailed walkthrough on the wiki[1] with links into SVN for
browsing the code. I think this is sufficient for understanding and
learning etc.

Note the dOSGi samples are a bit different from the core CXF demos in
that the emphasis is on the simplicity of enabling pre-existing OSGi
code for distribution. So the actual application code is really of
secondary importance. The crucial thing is the few knobs that need to
be set in order to transparently expose or consume an OSGi service as
a remote web service.



View raw message