Hi William

Ok, I haven't thought about it that in Camel one may want to route say
JMS messages to it, so I will add a @transportId back...

> BTW, I found the @serviceClass does not work for JAXRS server

I think in JAXWS it's meant to point to a real class when Spring proxies
are used but since we introduced (Spring) proxy helper that attribute
has never been used in JAX-RS. In jaxrs:server you can register a list
of resource classes using serviceBeans (using a List programmatically).
But I do agree
It can be handy using @serviceClass when only a single resource class is
used, this simplifying a configuration a bit.

Thanks, Sergey 

-----Original Message-----
From: Willem Jiang [mailto:[email protected]] 
Sent: 30 May 2009 06:23
To: [email protected]
Subject: Re: Question about the JAXRS client's schema

Hi Sergey,

I think we may need to use the @transportId if we want to configure
the transport for JAXRS endpoint, such as JMS transport or local
transport.

BTW, I found the @serviceClass does not work for JAXRS server, and I'm
heading to fix it.

Willem

Sergey Beryozkin wrote:
> Hi Willem
> 
>> <xsd:element name="invoker" type="xsd:anyType" minOccurs="0"/>
> 
> This one is a copy and paste error. I just removed it from
jaxrs:client.
> I also removed the following from jaxrs:server :
> 
> jaxrs:binding 
> jaxrs:serviceFactory
> @transportId
> @bindingId
> @endpointName
> @serviceName
> 
> as they most likely made it into jaxrs:server as a result of copying
> from jaxws:endpoint. We may end up adding some of these
> elements/attributes back, but at the moment we just don't use them...
> 
> thanks for raising the issue on the dev list
> Sergey  
>  
> 
> -----Original Message-----
> From: Willem Jiang [mailto:[email protected]] 
> Sent: 26 May 2009 04:06
> To: [email protected]
> Subject: Question about the JAXRS client's schema
> 
> Hi Sergey,
> 
> I'm working on integrating the CXF JAXRS with Camel, and just found
> there are some elements which are defined in the JAXRS client are
> useless.
> such as
> <xsd:element name="executor" type="xsd:anyType" minOccurs="0"/>
> <xsd:element name="invoker" type="xsd:anyType" minOccurs="0"/>
> 
> Did I miss something ?
> 
> Thanks,
> 
> Willem
> 

Reply via email to