Hi Sergey,
Sorry for the discomfort this has caused. I never meant to hurt anyone
on this forum.
You have been providing outstanding support in making the CXF JAX-RS
implementation more robust and feature rich and compelling choice for
CXF users.
I have been liking both these frameworks and I personally like to use
CXF when it comes to providing unified access to SOAP & REST web
services, which forms the crux for this variant. I am a big fan of CXF
for quite sometime now and I always wanted CXF JAXRS to be more
successful, personally knowing it has nice feature set and has the
potential for more innovation than any other frameworks can offer in
this space.
I am really excited about 2.2 since it fully supports JSR311 API and not
to mention that I blogged [1] recently about this.
Thanks!
Arul
[1] http://aruld.info/cxf-22-in-action-services-design-simplified/
Sergey Beryozkin wrote:
Hi Arul
By the way, I've no problems at all with users choosing alternative
implementations. I guess I might've been uncomfortable with it - but I'm
much less so today.
I know we're getting pretty strong, though a lot of work still has to be
done, but we have the ideas on how to move forward.
For ex, combining SOAP & REST services is just one of the areas where
we'll try to innovate but we'll work hard to make sure CXF JAXRS gets
good reviews in time on its own too.
Your enthusiastic approach toward experimenting with multiple frameworks
and encouraging implementers is fantastic - thanks a million and sorry
if I overreacted :-)
cheers, Sergey
You may want to try disabling Jersey classpath scanning for
resources and providers and instead use PackagesResourceConfig.
This can be done by configuring web.xml:
<servlet>
<servlet-name>Jersey Web Application</servlet-name>
<servlet-class>com.sun.jersey.spi.container.servlet.ServletContainer</se
rvlet-class>
<init-param>
<param-name>com.sun.jersey.config.property.packages</param-name>
<param-value>rest.resources;rest.providers</param-value>
</init-param>
</servlet>
-Arul
