You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Kiren Pillay <ki...@gmail.com> on 2011/11/21 11:00:54 UTC
JAX-RS and .NET
Hi
We have a partner running .NET, who is trying to integrate with our
REST-ful cxf web services. Their toolset can consume WSDL only and not
WADL.
Can someone recommend the easiest way for them to integrate with us?
Regards
Kiren
Re: JAX-RS and .NET
Posted by Sergey Beryozkin <sb...@gmail.com>.
On 21/11/11 11:27, Kiren Pillay wrote:
> Thanks Sergei,
>
> It is possible for them to do it but with a little bit of coding
> required on their side (Not as easy as a SOAP webservice).
>
> We won't have time to try your recommended suggestion, sounds like
> quite an involved bit of work:)
>
That is actually not that difficult :-), but I've just realized that
there's a much simpler option available,
jaxrs:server/@docLocation can reference documents such as WADLs, but
nothing blocks it from referencing an existing WSDL doc, the only
problem is that it is still a WADLGenerator which will serve this
document, so a .NET code would need to use a query like this:
"someaddress?_wadl" which can be easily changed to say
"someaddress?wsdl" with a "wsdl" query changed to a "_wadl" on the
server side in the custom cxf interceptor
Cheers, Sergey
> Regards
> Kiren
>
> On Mon, Nov 21, 2011 at 12:27 PM, Sergey Beryozkin<sb...@gmail.com> wrote:
>> Hi,
>>
>> On 21/11/11 10:00, Kiren Pillay wrote:
>>>
>>> Hi
>>>
>>> We have a partner running .NET, who is trying to integrate with our
>>> REST-ful cxf web services. Their toolset can consume WSDL only and not
>>> WADL.
>>>
>>
>> Is it WSDL 2.0 that their toolset supports ?
>>
>>> Can someone recommend the easiest way for them to integrate with us?
>>>
>> Perhaps the simplest option in this case is to transform a generated WADL
>> into a corresponding WSDL2 document.
>> Right now, it's not possible to use XSLTJaxbProvider in combination with
>> WADLGenerator which would only require registering a stylesheet which can do
>> the transformation, CXF may even ship such a stylesheet.
>>
>> So a bit more work is needed at the moment, you'd need to explicitly
>> register a WADLGenerator (as a jaxrs:provider), set an
>> "ignoreMessageWriters" property on it to false, and also register a custom
>> MessageBodyWriter<String> implementation with
>> @Produces(WADLGenerator.WADL_TYPE). This provider will then use a custom
>> stylesheet to transform a string wadl representation into WSDL 2.0 doc, a
>> generic stylesheet may become quite involved but the one optimized to handle
>> an individual WADL doc will be simple enough
>>
>> Hope it helps, Sergey
>>
>>
>>
>>> Regards
>>> Kiren
>>
>>
>> --
>> Sergey Beryozkin
>>
>> http://sberyozkin.blogspot.com
>>
>> Talend Community Coders
>> http://coders.talend.com/
>>
--
Sergey Beryozkin
http://sberyozkin.blogspot.com
Talend Community Coders
http://coders.talend.com/
Re: JAX-RS and .NET
Posted by Kiren Pillay <ki...@gmail.com>.
Thanks Sergei,
It is possible for them to do it but with a little bit of coding
required on their side (Not as easy as a SOAP webservice).
We won't have time to try your recommended suggestion, sounds like
quite an involved bit of work:)
Regards
Kiren
On Mon, Nov 21, 2011 at 12:27 PM, Sergey Beryozkin <sb...@gmail.com> wrote:
> Hi,
>
> On 21/11/11 10:00, Kiren Pillay wrote:
>>
>> Hi
>>
>> We have a partner running .NET, who is trying to integrate with our
>> REST-ful cxf web services. Their toolset can consume WSDL only and not
>> WADL.
>>
>
> Is it WSDL 2.0 that their toolset supports ?
>
>> Can someone recommend the easiest way for them to integrate with us?
>>
> Perhaps the simplest option in this case is to transform a generated WADL
> into a corresponding WSDL2 document.
> Right now, it's not possible to use XSLTJaxbProvider in combination with
> WADLGenerator which would only require registering a stylesheet which can do
> the transformation, CXF may even ship such a stylesheet.
>
> So a bit more work is needed at the moment, you'd need to explicitly
> register a WADLGenerator (as a jaxrs:provider), set an
> "ignoreMessageWriters" property on it to false, and also register a custom
> MessageBodyWriter<String> implementation with
> @Produces(WADLGenerator.WADL_TYPE). This provider will then use a custom
> stylesheet to transform a string wadl representation into WSDL 2.0 doc, a
> generic stylesheet may become quite involved but the one optimized to handle
> an individual WADL doc will be simple enough
>
> Hope it helps, Sergey
>
>
>
>> Regards
>> Kiren
>
>
> --
> Sergey Beryozkin
>
> http://sberyozkin.blogspot.com
>
> Talend Community Coders
> http://coders.talend.com/
>
Re: JAX-RS and .NET
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi,
On 21/11/11 10:00, Kiren Pillay wrote:
> Hi
>
> We have a partner running .NET, who is trying to integrate with our
> REST-ful cxf web services. Their toolset can consume WSDL only and not
> WADL.
>
Is it WSDL 2.0 that their toolset supports ?
> Can someone recommend the easiest way for them to integrate with us?
>
Perhaps the simplest option in this case is to transform a generated
WADL into a corresponding WSDL2 document.
Right now, it's not possible to use XSLTJaxbProvider in combination with
WADLGenerator which would only require registering a stylesheet which
can do the transformation, CXF may even ship such a stylesheet.
So a bit more work is needed at the moment, you'd need to explicitly
register a WADLGenerator (as a jaxrs:provider), set an
"ignoreMessageWriters" property on it to false, and also register a
custom MessageBodyWriter<String> implementation with
@Produces(WADLGenerator.WADL_TYPE). This provider will then use a custom
stylesheet to transform a string wadl representation into WSDL 2.0 doc,
a generic stylesheet may become quite involved but the one optimized to
handle an individual WADL doc will be simple enough
Hope it helps, Sergey
> Regards
> Kiren
--
Sergey Beryozkin
http://sberyozkin.blogspot.com
Talend Community Coders
http://coders.talend.com/