cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <>
Subject Re: svn commit: r1412802
Date Fri, 23 Nov 2012 14:03:06 GMT

I'll probably stay away for a moment from getting JAX-RS endpoints 
auto-detected given that the default context path will not be really 
user friendly in such cases (ex, 'my_company_Books', etc) though this 
can work ok in a end-to-end WS case...

However supporting JAX-RS Application OSGI services will make sense, 
something I can work upon in time...

The question is, are we prepared to get DSW depending on JAX-WS & JAX-RS 
API ? I don't see any major issues at the moment, it probably will do OK

Thanks, Sergey

On 23/11/12 12:24, Christian Schneider wrote:
> In the DOSGI-128 issue I do not plan to support a default address.
> There is anothe issue for it though:
> I planned to use the servlet transport by default and somehow create the
> default address from the Service interface. Not sure how to support more
> than one instance of a service endpoint for the same interface though.
> Still we could simply start with that.
> Christian
> Am 23.11.2012 11:52, schrieb Sergey Beryozkin:
>> 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:
>> 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 '' annotation that
>> can identify a service bean as a JAX-RS root resource
>> class...Alternatively the service bean itself can be
>> ''. 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

Sergey Beryozkin

Talend Community Coders


View raw message