Hi -
On 07/10/11 21:53, K Fung wrote:
Hi Sergey,
Thank you for the feedback.
I'll work on getting the code compilable in the examples folder and
then submit a JIRA task to track its submission into trunk. I'll
definitely include a README to talk about it does (which I presume
will be the basis for the wiki page).
The initial scope for the the sample code would be to demonstrate a
"Hello World" type of application but I would definitely want to
extend it to include some of the more common features utilized (e.g.,
JAXB) so that consuming teams don't need to go through as much work as
I did to initially get this code to work.
Yes, please create a JIRA and attach the contribution there and we can
then review what is the best way to handle it.
FYI, this example works fine in both Eclipse Equinox and Apache Felix
so it isn't tied to a particular OSGI runtime.
Sounds good. FYI, the demos I mentioned run in Karaf which can use
either Equinox or Felix. I'm wondering though how the use of ServiceMix
bundles can be avoided as they are just proper OSGI bundles, so look
forward to seeing the example :-)
Thanks, Sergey
Regards,
kl
On Fri, Oct 7, 2011 at 1:29 PM, Sergey Beryozkin<sberyoz...@gmail.com> wrote:
Hi
I think I like all the options you suggested :-)
Please see comments inline
On 07/10/11 19:51, K Fung wrote:
Hi everyone,
(long time lurker here ... thought it was about them we started to
contribute something back)
As everyone who's played with CXF JAX-RS and OSGI knows, it's not too
easy to get CXF and OSGI to co-operate outside of the Apache
ServiceMix bundle/example.
I've been sitting on a CXF JAX-RS OSGI example for the last few months
that illustrates the minimal dependencies needed for CXF JAX-RS OSGI
to work correctly but I don't know what's the best way to distribute
it.
As it's a combination of both CXF JAX-RS code and ServiceMix code,
it's in the middle ground where it neither fits with ServiceMix nor
CXF perfectly. So I'm looking for feedback about where you think this
sample would fit best?
Some thoughts I had...
1) As an example in the CXF distribution
This one seems like the best candidate initially - we can have a look then
and see if some of the contribution which is generic enough can be pushed to
the trunk(s)
2) As an entry in the CXF wiki
(https://cwiki.apache.org/confluence/display/CXF)
Sounds good - if the contribution will have a Readme then I can help with
creating a wiki page too
3) As just a blog entry somewhere in the world wide web where it may
be referenced
+1 :-)
Do any of you have any thoughts? Would it even be welcomed in the CXF
trunk?
Dan has been doing a lot of work with regard to the OSGI-fication of CXF. I
think sooner or later most of CXF core modules will be very OSGI
proactive/aware. One thing I hope the jaxrs module will be able to do is to
discover JAX-RS Application or Provider services (the latter is possible
with DOSGi CXF), and do some other cool dynamic OSGI things. So if we can
identify some generally useful code then we can start pushing it to the
trunk.
All the JAX-RS demos we ship with the Talend Examples distro are OSGI-aware
but indeed they all do depend on ServiceMix bundles
Many thanks, Sergey
Regards,
kl
