Hi
On 23/11/12 10:15, Christian Schneider wrote:
Hi Sergey,
the idea is to auto detect if a service is a JAXWS service by detecting
the @WebService annotation.
So if this annotation is found then the service would default to
JAXWS/JAXB instead of Simple/Aegis if no intent overrides this.
The corresponding issue is:
https://issues.apache.org/jira/browse/DOSGI-128
OK, see what you mean, thanks
This may also be possible for JAXRS. Can you open an issue and document
how a jaxrs service should be detected and what the settings then should be?
In case of JAX-RS, it has to be '@javax.ws.rs.Path' annotation that can
identify a service bean as a JAX-RS root resource class...Alternatively
the service bean itself can be 'javax.ws.rs.core.Application'. I guess
I can definitely get the code enhanced to manage 'Application' OSGI
services, however, what about the auto-detection and the actual endpoint
address ?
Will the endpoint be bound to HTTP Service or will it be an absolute
(default) URI and thus Jetty will do an internal HTTP support ?
Thanks, Sergey
Christian
On 11/23/2012 10:59 AM, Sergey Beryozkin wrote:
Hi Christian
What is the auto-detection and is there any reason JAX-RS endpoints
can not benefit of this possible enhancement ?
Thanks, Sergey
On 23/11/12 09:50, cschnei...@apache.org wrote:
Author: cschneider
Date: Fri Nov 23 09:50:25 2012
New Revision: 1412802
URL: http://svn.apache.org/viewvc?rev=1412802&view=rev
Log:
DOSGI-128 Small refactoring in preparation of the auto detection of
jaxws and jaxb services
