Hi,
On 08/06/12 15:30, Daniel Kulp wrote:
On Thursday, June 07, 2012 02:56:01 AM n99 wrote:
Thanks for that
I will try the interceptor.
But I'd like to the query the docs at:
http://cxf.apache.org/docs/jax-rs-data-bindings.html#JAX-RSDataBindings-CX
FDataBindingsasJAXRSproviders
Interesting. I didn't even know about that. Cool. More stuff Sergey did
when I wasn't watching... :-)
:-), this JAXRSDataBinding provider was added when one user said that he
wrote an optimized non-JAXB XML binding provider for a JAX-RS endpoint
and wanted to use it for processing SOAP requests too.
This provider can manage simple SOAP payloads only, but it's definitely
for very specific use cases.
Not sure what the issue is. The XSLTJaxbProvider may not be able to handle
the XMLStreamReader/Writer forms that the JAX-WS side of things require.
In JAX-RS, the providers generally use the raw streams with only a couple
updated to also handle StAX.
I have a test working now with the JAXWS frontend posting a payload and
the JAXWS frontend effectively delegating to XSLTJaxbProvider to
read/write the data available inside of soap:envelope, there were few
issues there, but I do not think there were anything to do with the JAXB
context not seeing some of the classes.
n99, I guess you should proceed with what Dan advised earlier on about
using XSLT on the JAX-WS path, but please test if you are still
interested in a day or so, the few minor fixes I'm about to commit would
be useful for JAX-RS endpoints using XSLTJAXBProvider too
Thanks, Sergey
Dan
the config says
<jaxws:endpoint xmlns:s="http://hello.com";
serviceName="s:HelloWorld"
endpointName="s:HelloWorldPort"
id="hello_soap-databinding"
implementor="org.apache.cxf.systest.jaxrs.jaxws.HelloWorldImpl"
address="/hello-soap-databinding">
<jaxws:dataBinding>
<ref bean="jaxrs-data-binding"/>
</jaxws:dataBinding>
</jaxws:endpoint>
<bean id="jaxrs-data-binding"
class="org.apache.cxf.jaxrs.provider.JAXRSDataBinding">
<property name="provider" ref="jaxbProviderSoap"/>
</bean>
<bean id="jaxbProviderSoap"
class="org.apache.cxf.jaxrs.provider.JAXBElementProvider"/>
which I think shows a JAX-RS provider being used ultimately in a CXF
DataBinding object?
Specifically it shows:
a org.apache.cxf.jaxrs.provider.JAXBElementProvider being wired into a
org.apache.cxf.jaxrs.provider.JAXRSDataBinding being used in a
jaxws:dataBinding in a jaxws:endpoint
I was configuring:
a org.apache.cxf.jaxrs.provider.XSLTJaxbProvider being wired into a
org.apache.cxf.jaxrs.provider.JAXRSDataBinding being used in a
jaxws:dataBinding in a jaxws:endpoint
.....and org.apache.cxf.jaxrs.provider.XSLTJaxbProvider is a subclass of
org.apache.cxf.jaxrs.provider.JAXBElementProvider.......?
Cheers
--
View this message in context:
http://cxf.547215.n5.nabble.com/Using-jaxrs-XSLTJaxbProvider-with-jaxws-e
ndpoint-through-JAXRSDataBinding-Is-it-possible-tp5709183p5709344.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
Blog: http://sberyozkin.blogspot.com
