One of the possible solutions I tried, was writing an interceptor.
This did not result in sending an query-string.
Should such an approach work?
public class QueryParamInterceptor extends AbstractPhaseInterceptorMessage
{
public QueryParamInterceptor(String phase) {
super(phase);
I would suggest adding a
.unmarshal(jaxb) before the xpath
where
jaxb = new JaxbDataFormat();
jaxb.setContextPath(..your context path..);
or using the PAYLOAD-mode in your cxf-endpoint.
--
View this message in context:
it shoud be a .marshal(jaxb) in stead of an .unmarshal(jaxb), of course, as
the direction is serializing.
--
View this message in context:
http://camel.465427.n5.nabble.com/XPath-with-CXF-Pojo-Endpoint-tp5743861p5743906.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I am asked to send a SOAP-call to:
https://yyy.xxx.net/Webservices/Xxx/XxxWebService.asmx?apk=myapkoid=myoidgoid=mygoid
I am using a camel-cxf endpoint, POJO-mode, Java DSL based routes.
What is the most appropriate way to supply the required query parameters?
Rene Avontuur
--
View this
