Hi, this demo is on the trunk now, I tested it and it worked fine
Thanks for this contribution,
Cheers, Sergey
On 16/12/11 22:34, K Fung wrote:
Hello,
I'm sorry - I should've put it into 2.5.1 - but it will definitely make
it into 2.5.2 - and I hope it would be of interest to users.
No worries Sergey. Thanks for all your helpful suggestions and guidance
while I worked on this in 2 week spurts.
It took us countless hours and much frustration to figure out how to run
CXF JAX-RS in our OSGI environment. Hopefully this sample will alleviate
the time needed for others to get up to speed with CXF JAX-RS in their own
environments.
In 2.5.2 on later we can think of introducing an activator into the jaxrs
frontend so that it can discover custom Applications and providers
registered as OSGI services
Perhaps we should have a discussion on a separate thread to discuss how you
envision seeing this? In particular, I'm wondering what's the
baseline/environment you think this would be running. For example, right
now there is no activator in the CXF JAX-RS bundle but what are the
consequence of an activator in 2.5.2+ - can it be disabled? Do we rely on
the OSGI HttpService or do we use a built-in Jetty? Can we support both?
I guess you can see that I'm pretty interested in this topic :-)
On Fri, Dec 16, 2011 at 2:21 PM, Sergey Beryozkin<sberyoz...@gmail.com>wrote:
Hi KL
On 16/12/11 22:13, K Fung wrote:
Hi Sergey,
I've uploaded the final version (for now) to CXF-3859. I've bumped up the
version to 2.5.2-SNAPSHOT and commented out the Apache Snapshot
repository.
Hopefully, this meets the quality bar for commit :-)
I'm sorry - I should've put it into 2.5.1 - but it will definitely make it
into 2.5.2 - and I hope it would be of interest to users.
I did investigate creating the JAXRSServerFactoryBean directly (instead of
subclassing CXFNonSpringJaxrsServlet). If I went down this route, I would
have had to include a dependency on Jetty directly (as the traffic
wouldn't
be provided via the OSGI HttpService) or duplicate much of the servlet
code
in CXFNonSpringJaxrsServlet. In the end, I decided that it just wasn't
worth it.
Sounds right...
In 2.5.2 on later we can think of introducing an activator into the jaxrs
frontend so that it can discover custom Applications and providers
registered as OSGI services
thanks, Sergey
Cheers,
kl
On Mon, Dec 5, 2011 at 9:39 AM, Sergey Beryozkin<sberyoz...@gmail.com**
wrote:
Hi KL
On 03/12/11 00:50, K Fung wrote:
Hi Sergey,
Adding Dynamic-Import: * would likely resolve the issue. It also makes
any
package/class name resolution a lot slower because all the OSGI bundles
will basically now be a gigantic class path. I would not be inclined to
go
down this route.
I've uploaded a new version to CXF-3859. I've updated the code so that
it
compiles in Java 5 (turns out this wasn't too hard once I figured how
ServiceMix got it to work) and now when you compile the samples pom.xml,
it'll also compile the JAX-RS Minimal OSGI sample.
The final things on my TODO list are to investigate how to avoid using
my
own special servlet and the removal the snapshot repository. For the
latter, I'll likely just comment this out since it turns out that in the
samples pom.xml, snapshots are enabled.
Please try commenting it out. It seems like it's ready for a commit,
thanks, Sergey
Regards,
kl
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
