Hi Dan,
What we do in camel-cxf is try to reuse everything what CXF can provide.
First we use the cxf-simple-front and cxf-jaxws-front endpoint to export
or consumer the WS services, then we provides MESSAGE, and PAYLOAD
DataFormat by massage the interceptors ourself, then we have cxfBeans,
cx
As another option, you can use the cxfbean compound but your bean
needs to have JAXWS annotations.
http://localhost:9090?matchOnUriPrefix=true"; />
Please see the unit test here:
https://svn.apach
I could be wrong but I think when camel-cxf PAYLOAD mode was developed,
the CXF Dispatch/Provider interface support wasn't quite ready (or we
haven't done enough due diligence). I agreed with you the benefit. We
could rewriting it using the Dispatch/Provider APIs. However, I
seriously doubt
tion {
> InputStream request =
> exchange.getIn().getBody(InputStream.class);
> InputSource is = new InputSource(request);
> Element payload = (Element) xpathExpression.evaluate(is,
> XPathConstants.NODE);
> JAXBElement el = (JAXBElement)
> unmarshaller.unmarshal(payload);
> Object o = el.getValue();
> exchange.getIn().setBody(o);
> }
>
> }
>
>
>
--
View this message in context:
http://old.nabble.com/Easy-One-way-soap-services-tp27233386p27261053.html
Sent from the Camel - Users mailing list archive at Nabble.com.
You could also create a SOAPDataFormat which extends JAXBDataFormat
which I think would be a good choice.
Then the JAXBDataFormat is still pure and clean in terms of JAXB.
And the SOAPDataFormat can over time have additional SOAP related stuff in it.
The code can still be in camel-jaxb if you do
Hi Christian,
I think it dependents what you want to do for further enhancement of the
your current solution. If you just want to add or strip the SOAP , an
option of the JAXB DataFormat could be enough.
If you want to do more enhancement, you'd better create a SOAP
DataFormat for it.
Willem
Hi Willem and Claus,
I have looked into the JaxbDataformat to see what I should implement. As
what I need to do for the new DataFormat is quite similiar to the
JaxbDataFormat I think two aproaches may help to avoid duplicate code.
1) I could create a processor that only removes or adds the SO
tsrats: Dr. Bernhard Beck
> Geschäftsführer: Jochen Adenau, Dr. Peter Krampf
>
> -Ursprüngliche Nachricht-
> Von: Willem Jiang [mailto:willem.ji...@gmail.com]
> Gesendet: Mittwoch, 20. Januar 2010 15:47
> An: users@camel.apache.org
> Betreff: Re: Easy One way soap service
Beck
Geschäftsführer: Jochen Adenau, Dr. Peter Krampf
-Ursprüngliche Nachricht-
Von: Willem Jiang [mailto:willem.ji...@gmail.com]
Gesendet: Mittwoch, 20. Januar 2010 15:47
An: users@camel.apache.org
Betreff: Re: Easy One way soap services
Maybe we can add a SOAP data formate to deal with
Maybe we can add a SOAP data formate to deal with the soap envelop out
of box.
BTW, It could be easy to just take off or put on the soap envelop.
But if there any WS* work involved, you had to switch to more flexible
way ( to use camel-cxf component).
Willem
Claus Ibsen wrote:
On Wed, Jan 20
On Wed, Jan 20, 2010 at 3:03 AM, Willem Jiang wrote:
> Hi Christian,
>
> Your processor implements a easy way to unmarshal the soap message.
> But I think you can leverage JAXB DataFormat to do the same thing, all you
> need to do is using a camel-xslt component for soap envelop transformation.
>
Hi
On Tue, Jan 19, 2010 at 10:53 PM, Christian Schneider
wrote:
> Hi all,
>
> I am thinking about how to make one way services easier. Currently I
> generate code for the service using cxf codegen and use the camel-cxf module
> to create a client or endpoint that can be routed over jms using the
Hi Christian,
Your processor implements a easy way to unmarshal the soap message.
But I think you can leverage JAXB DataFormat to do the same thing, all
you need to do is using a camel-xslt component for soap envelop
transformation.
Willem
Christian Schneider wrote:
Hi all,
I am thinking
Hi all,
I am thinking about how to make one way services easier. Currently I
generate code for the service using cxf codegen and use the camel-cxf
module to create a client or endpoint that can be routed over jms using
the camel-jms component. Using CXF for this task is a little overkill as
v
14 matches
Mail list logo