Kumar
>
> On Thu, Apr 8, 2021 at 5:38 PM Claus Ibsen wrote:
>
>> What Camel and CXF version are you using?
>>
>> On Thu, Apr 8, 2021 at 11:53 AM Anand Kumar
>> wrote:
>> >
>> > Hi Team
>> >
>> >
>> > We are getting belo
> > We are getting below error while calling REST service using camel-cxf
> component
> >
> > java.lang.RuntimeException: java.util.ConcurrentModificationException
> > at
> org.apache.cxf.jaxrs.client.JAXR
What Camel and CXF version are you using?
On Thu, Apr 8, 2021 at 11:53 AM Anand Kumar wrote:
>
> Hi Team
>
>
> We are getting below error while calling REST service using camel-cxf
> component
>
> java.lang.RuntimeException: java.util.Concurr
Hi Team
We are getting below error while calling REST service using camel-cxf component
java.lang.RuntimeException: java.util.ConcurrentModificationException
at
org.apache.cxf.jaxrs.client.JAXRSClientFactoryBean.createWebClient(JAXRSClientFactoryBean.java:233
Hi,
How can this be fixed? What I see is that the custom error handler is not
getting picked up by the cxf components (REST & SOAP). Is there a option in cxf
component for this?
Regards,
Vikas
From: Vikas Jaiswal
Sent: 26 March 2020 10:12
To: 'users@camel.apache.org'
Subject: Jetty ba
Hi
I have a issue with the Jetty banner that comes up while a 404 error
occurs. This is what I did to fix it:
1) Extended org.eclipse.jetty.server.handler.ContextHandler to create a
custom contexhandler.
2) This custom context handler is configured in camel-config.xml (I
Hi,
Is there any document or resource available on performance metrics of
Camel? I am specifically looking for cxf component performance metrics.
Regards,
Vikas Jaiswal
Lead Consultant
T: +91 9371626126 |Saksoft Ltd
[cid:image002.png@01D5B658.6760C4B0]
Hello,
I'using cxf component as producer to access a SOAP service. In case of
soap faults I need to access the reason of the fault.
I'm using PAYLOAD dataformat.
I tried several options but SoapFault.class is never fired. I can find
it in the ip packets using wireshark.
The only exception fired
Solved,
specify soap version 1.2 do the job.
I added the following line to the cxfEndpoint:
Regards
Alberto
On Wed, 2016-07-06 at 10:52 +0200, Alberto wrote:
> Hello,
>
> I'm using the cxf component as producer in dispatch mode as specify
> in
> http://c
Hello,
I'm using the cxf component as producer in dispatch mode as specify in
http://camel.apache.org/cxf.html.
The endpoint:
http://hostname/servi
ce/soap">;
The relevant part of the route:
.s
you can configure cxf features at the camel-cxf endpoint as well.
http://camel.apache.org/cxf.html
2015-09-03 9:59 GMT+02:00 Rafik EL YAAGOUBI (contractor)
<rafik.elyaago...@amadeus.com>:
> Hello,
>
> I'm using Camel 15.2, I would like to use camel-cxf component in CXF D
Hello,
I'm using Camel 15.2, I would like to use camel-cxf component in CXF Dispatch
mode and enable CXF features, should I configure a custom bus or is there any
way to declare features directly in the endpoint?
Thank you.
Regards,
Rafik EL YAAGOUBI
No further comments? :)
--
View this message in context:
http://camel.465427.n5.nabble.com/SOAP-headers-not-relayed-for-a-SOAP-1-2-service-when-using-CXF-component-tp5765823p5765987.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi!
I'm using Camel 2.15.0 and the CXF component (CXF 3.0.4) to call a SOAP 1.2
web service in PAYLOAD mode. The call in itself works fine, however
necessary out of band soap headers (i.e. not defined in the contract) are
not relayed to the service endpoint for some reason.
In the log I can see
,
urn:test:namespace);
--
View this message in context:
http://camel.465427.n5.nabble.com/SOAP-headers-not-relayed-for-a-SOAP-1-2-service-when-using-CXF-component-tp5765823p5765846.html
Sent from the Camel - Users mailing list archive at Nabble.com.
, 2015 at 9:28:44 PM, _redwings (eriknygre...@gmail.com) wrote:
Hi!
I'm using Camel 2.15.0 and the CXF component (CXF 3.0.4) to call a SOAP 1.2
web service in PAYLOAD mode. The call in itself works fine, however
necessary out of band soap headers (i.e. not defined in the contract
:
http://camel.465427.n5.nabble.com/Calling-NTLM-protected-service-from-camel-cxf-component-tp5765161p5765179.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Best regards,
Sergeymailto:szh.s...@gmail.com
}
serviceClass=com.myresouce.Resource
loggingFeatureEnabled=true /
/beans
--
View this message in context:
http://camel.465427.n5.nabble.com/Calling-NTLM-protected-service-from-camel-cxf-component-tp5765161.html
Sent from the Camel - Users mailing list archive
-service-from-camel-cxf-component-tp5765161.html
Sent from the Camel - Users mailing list archive at Nabble.com.
-from-camel-cxf-component-tp5765161p5765179.html
Sent from the Camel - Users mailing list archive at Nabble.com.
-cxf-component-sending-to-soap-endpoint-tp5764460p5764630.html
Sent from the Camel - Users mailing list archive at Nabble.com.
this problem even with much bigger files)
Are there any hints you can give on how to monitor (probably with some jmx
metrics camel/cxf/errorhandlers offers) stack size or work load?
--
View this message in context:
http://camel.465427.n5.nabble.com/StackOverflowException-for-route-using-cxf
to lines in our code i hope
someone of you can help.
thanks in advance
--
View this message in context:
http://camel.465427.n5.nabble.com/StackOverflowException-for-route-using-cxf-component-sending-to-soap-endpoint-tp5764460.html
Sent from the Camel - Users mailing list archive
Faults
handled before?! Since there is no reals hint to lines in our code i hope
someone of you can help.
thanks in advance
--
View this message in context:
http://camel.465427.n5.nabble.com/StackOverflowException-for-route-using-cxf-component-sending-to-soap-endpoint-tp5764460.html
Sent from
quite happy to make the fixes. What's the best format to
submit the
fix
- patch or pull request?
Thanks,
Paul
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified
this message in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952p5759332.html
Sent from the Camel - Users mailing list archive at Nabble.com.
,
Paul
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952p5759332.html
Sent from the Camel - Users mailing list archive at Nabble.com.
someone re-open the JIRA task? Or should I log a new one?
I'm quite happy to make the fixes. What's the best format to submit
the
fix
- patch or pull request?
Thanks,
Paul
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF
in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952p5759332.html
Sent from the Camel - Users mailing list archive at Nabble.com.
- patch or pull request?
Thanks,
Paul
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952p5759332.html
Sent from the Camel - Users mailing list archive at Nabble.com.
) - the same issue.
Can someone re-open the JIRA task? Or should I log a new one?
I'm quite happy to make the fixes. What's the best format to submit the fix
- patch or pull request?
Thanks,
Paul
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment
.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952p5759332.html
Sent from the Camel - Users mailing list archive at Nabble.com.
WSS4J?
3. Can I use Java DSL? The examples seem to be in Spring xml.
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Questions-about-CXF-component-tp5756202.html
Sent from the Camel - Users mailing list archive at Nabble.com.
in context:
http://camel.465427.n5.nabble.com/Apache-Camel-v2-12-CXF-Component-Basic-Authentication-Web-Service-tp5746233p5756115.html
Sent from the Camel - Users mailing list archive at Nabble.com.
loos like it's the cxf behaviour to decode the base64. but I could not find
this in cxf docs.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-component-is-encoding-base64-by-default-tp5750705p5752303.html
Sent from the Camel - Users mailing list archive
like it's the cxf behaviour to decode the base64. but I could not find
this in cxf docs.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-component-is-encoding-base64-by-default-tp5750705p5752303.html
Sent from the Camel - Users mailing list archive
service using the camel-cxf component. Below is how
the element defined in
wsdl.
xs:element name=elementA
ns1:expectedContentTypes=application/octet-stream type=xs:base64Binary
xmlns:ns1=http://www.w3.org/2005/05/xmlmime/
javaCode:
element A is encoded base64 String
DataHandler dataHandler = new
Hi,
maybe someone will correct me, but I think thats not an issue of the
camel-cxf component.
Cxf uses jaxb as standard binding and jaxb has a standard schema to java
type mapping:
See the chapter Schema-to-Java Mapping of the following link:
http://docs.oracle.com/cd/E19159-01/819-3669/bnazf
Hi ,
I am consuming the web service using the camel-cxf component. Below is how
the element defined in
wsdl.
xs:element name=elementA
ns1:expectedContentTypes=application/octet-stream type=xs:base64Binary
xmlns:ns1=http://www.w3.org/2005/05/xmlmime/
javaCode:
element A is encoded base64 String
format is not POJO with MTOM enabled
if (cxfMessage.getAttachments() != null
!(DataFormat.POJO.equals(dataFormat) !isXop)) {
// propagate attachments
/
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified
not use MTOM:
if dataFormat is POJO and properties.mtom-enabled is false, propagate the
attachments into and from the camel Exchange.
Thank you.
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952
in context:
http://camel.465427.n5.nabble.com/CXF-component-attachment-support-for-POJO-not-implemented-as-specified-tp5746952.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Camel Experts,
I'd like to know how and where to configure cxf component to use proxy. I'm
using cxf component to invoke a web service which is hosted on the internet
and is behind our corporate proxy. I'm afraid if there is no such way as of
now. My Camel version is - 2.12.2.
I might get
--
View this message in context:
http://camel.465427.n5.nabble.com/Apache-Camel-v2-12-CXF-Component-Basic-Authentication-Web-Service-tp5746233p5746435.html
Sent from the Camel - Users mailing list archive at Nabble.com.
and Regards
Prince Manchanda
--
View this message in context:
http://camel.465427.n5.nabble.com/Apache-Camel-v2-12-CXF-Component-Basic-Authentication-Web-Service-tp5746233p5746392.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Looking at the CXF Component Documentation
http://camel.apache.org/cxf.html , I notice that two new options
(username and password) for Basic Authentication have been added in 2.12.3.
http://camel.465427.n5.nabble.com/file/n5746426/Untitled.png
However, from the download, I am not able
:
http://camel.465427.n5.nabble.com/Apache-Camel-v2-12-CXF-Component-Basic-Authentication-Web-Service-tp5746233p5746435.html
Sent from the Camel - Users mailing list archive at Nabble.com.
(authorization);
However, when I try to use Camel's CXF component to access the
same Web Service I get 401 Unauthorized error, since Camel is
not sending the authentication information to the Web Service.
My route looks like:
from(file://c:/test?fileName=request.txtnoop=true
);
conduit.setAuthorization(authorization);
However, when I try to use Camel's CXF component to access the same Web
Service I get 401 Unauthorized error, since Camel is not sending the
authentication information to the Web Service.
My route looks like:
from(file://c:/test?fileName
payloads and then create a
correct request and send it to the external web service
thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-Component-tp5738196.html
Sent from the Camel - Users mailing list archive at Nabble.com.
a soap
request,how do I factor out the message payloads and then create a
correct request and send it to the external web service
thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-Component-tp5738196.html
Sent from the Camel - Users mailing list
10:09
To: users@camel.apache.org
Subject: CXF Component
Hi,
I have the following route:
from(cxf://http://0.0.0.0:8080/proxy?dataFormat=MESSAGEserviceClass=com.ProxyClass;)
.process(new Processor() {
@Override
://camel.465427.n5.nabble.com/Replacing-standalone-client-with-generic-one-in-cxf-component-tp5735827p5736389.html
Sent from the Camel - Users mailing list archive at Nabble.com.
, feel free to ask.
Regards,
Kannaiah
--
View this message in context:
http://camel.465427.n5.nabble.com/Replacing-standalone-client-with-generic-one-in-cxf-component-tp5735827.html
Sent from the Camel - Users mailing list archive at Nabble.com
(http://Nabble.com).
-standalone-client-with-generic-one-in-cxf-component-tp5735827.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi All:
I have a question about the expect body type of CXF compoent when using
CXF_MESSAGE dataFormat. My CXF version is 2.7.5 and Camel version is 2.10.4.
for example, I have a route:timer - setBody (constant string content) -
CXF
It works fine, if dataFormat of this cxf component is RAW, POJO
CXF component
(dataFormat type is CXF_MESSAGE) sent a request msg without ws-addressing
information inside. then got a NullPointerException, the error msg is:
Exception in thread default-workqueue-1 java.lang.NullPointerException
://issues.apache.org/jira/browse/CAMEL-6404 .
Thanks.
2013/5/29 liugang594 Liu clevers...@gmail.com (mailto:clevers...@gmail.com)
If the required service with ws-addressing enable, and from CXF component
(dataFormat type is CXF_MESSAGE) sent a request msg without ws-addressing
information
service with ws-addressing enable, and from CXF
component
(dataFormat type is CXF_MESSAGE) sent a request msg without
ws-addressing
information inside. then got a NullPointerException, the error msg is:
Exception in thread default-workqueue-1
java.lang.NullPointerException
If the required service with ws-addressing enable, and from CXF component
(dataFormat type is CXF_MESSAGE) sent a request msg without ws-addressing
information inside. then got a NullPointerException, the error msg is:
Exception in thread default-workqueue-1 java.lang.NullPointerException
enable, and from CXF component
(dataFormat type is CXF_MESSAGE) sent a request msg without ws-addressing
information inside. then got a NullPointerException, the error msg is:
Exception in thread default-workqueue-1 java.lang.NullPointerException
It's easy to reproduce this problem:
use CXF component with CXF_MESSAGE dataFormat to call any service, and the
response of this service is a fault, then you can see this exception.
My camel version is 2.10.4, and cxf version is 2.7.5
2013/5/29 Willem jiang willem.ji...@gmail.com
From
Hi All:
I'd like to know how I can put the HTTP Authorization Setting on CXF
component.
1. On Consumer Side, I want to reuse the setting of Server
2. On Producer Side, I want to attach the Auth Info (username/password/auth
type) when sending the request.
Thanks in advance.
--
Thanks
GangLiu
/soap-env:Envelope
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-add-HTTP-Basic-and-Digest-Auth-on-CXF-component-tp5729234p5729272.html
Sent from the Camel - Users mailing list archive at Nabble.com.
The cxf component supports basic auth (we use it in one of our project).
Google will help you to find a code snippet...
Sent from a mobile device
Am 15.03.2013 23:27 schrieb santhosh ramukhsohtna...@gmail.com:
If you dont get it sorted out with a CXF client,the simplest way would be
send
this message in context:
http://camel.465427.n5.nabble.com/Websphere-6-1-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083p5726967.html
Sent from the Camel - Users mailing list archive at Nabble.com.
to the
exchange.getOut.setHeader(..) that can be prevented from propagating
as HTTP headers with the SOAP communication?
--
View this message in context:
http://camel.465427.n5.nabble.com/Websphere-6-1-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083p5726967.html
Sent from
to the WS caller from the CXF bean, and continue
processing, e.g. storing something on a queue etc.
--
View this message in context:
http://camel.465427.n5.nabble.com/Websphere-6-1-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083p5726981.html
Sent from the Camel - Users
Sriraman.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-component-Adding-custom-context-classes-via-the-uri-options-tp5726313p5726403.html
Sent from the Camel - Users mailing list archive at Nabble.com.
:
http://camel.465427.n5.nabble.com/Websphere-6-1-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cib...@redhat.com
.465427.n5.nabble.com/Websphere-6-1-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083p5726163.html
Sent from the Camel - Users mailing list archive at Nabble.com.
-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083p5726183.html
Sent from the Camel - Users mailing list archive at Nabble.com.
-cxf-component-POJO-mode-tp5726083.html
Sent from the Camel - Users mailing list archive at Nabble.com.
NB: Camel version: 2.6.0 (latest possible on Websphere 6.1).
--
View this message in context:
http://camel.465427.n5.nabble.com/Websphere-6-1-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083p5726084.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Cheers Willem.
Viktoras
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-fails-to-marshal-SOAP-fault-details-tp5718686p5718701.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I was facing a similar issue and the solution was very useful.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Component-with-ActiveMQ-tp474631p5718646.html
Sent from the Camel - Users mailing list archive at Nabble.com.
this message in context:
http://camel.465427.n5.nabble.com/CXF-component-fails-to-marshal-SOAP-fault-details-tp5718686.html
Sent from the Camel - Users mailing list archive at Nabble.com.
://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-fails-to-marshal-SOAP-fault-details-tp5718686p5718698.html
Sent from the Camel - Users mailing list archive at Nabble.com.
exchange = new DefaultExchange(camelContext);
exchange.getIn().setBody(message);
template.send(cxf:bean:helloService,exchange);
--
View this message in context:
http://camel.465427.n5.nabble.com/how-can-i-send-message-to-cxf-component-with-producerTemplate-tp5718227.html
Sent from
(message);
template.send(cxf:bean:helloService,exchange);
--
View this message in context:
http://camel.465427.n5.nabble.com/how-can-i-send-message-to-cxf-component-with-producerTemplate-tp5718227.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Charles Moulliard
Yogesh,
Thank you for the info! It should work.
regards,
Anton
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p4928987.html
Sent from the Camel - Users mailing list archive at Nabble.com.
);
senderExchange.getIn().setHeader(Client.REQUEST_CONTEXT ,
requestContext);
}
Cheers,
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p493.html
Sent from the Camel - Users mailing list archive
Hi,
I have a small issue with Camel CXF component supporting both SOAP bindings:
1.1 and 1.2.
If I take pure CXF service and specify:
@ServiceMode(value = Service.Mode.MESSAGE)
@BindingType(value = http://www.w3.org/2003/05/soap/bindings/HTTP/;)
this CXF Service accepts both kind of requests
fix it.
Freeman
On 2011-10-17, at 下午6:50, Andrei Shakirin wrote:
Hi,
I have a small issue with Camel CXF component supporting both SOAP
bindings: 1.1 and 1.2.
If I take pure CXF service and specify:
@ServiceMode(value = Service.Mode.MESSAGE)
@BindingType(value = http://www.w3.org/2003/05
Hi Freeman,
Yep, interceptor fixes the problem!
Regards,
Andrei.
-Original Message-
From: Freeman Fang [mailto:freeman.f...@gmail.com]
Sent: 17 October 2011 13:28
To: users@camel.apache.org
Subject: Re: Camel CXF component: SOAP 1.1 1.2 support
Hi,
My gut feeling is that this issue
: Freeman Fang [mailto:freeman.f...@gmail.com]
Sent: 17 October 2011 13:28
To: users@camel.apache.org
Subject: Re: Camel CXF component: SOAP 1.1 1.2 support
Hi,
My gut feeling is that this issue is kinda of similar with the one I
encountered with servicemix-cxf-bc JBI component(which means only
-10-17, at 下午8:07, Andrei Shakirin wrote:
Hi Freeman,
Yep, interceptor fixes the problem!
Regards,
Andrei.
-Original Message-
From: Freeman Fang [mailto:freeman.f...@gmail.com]
Sent: 17 October 2011 13:28
To: users@camel.apache.org
Subject: Re: Camel CXF component: SOAP 1.1 1.2 support
Thanks Freeman, I was too slow.
-Original Message-
From: Freeman Fang [mailto:freeman.f...@gmail.com]
Sent: 17 October 2011 14:45
To: users@camel.apache.org
Subject: Re: Camel CXF component: SOAP 1.1 1.2 support
FYI, I create CAMEL-4553 to track it.
[1]https://issues.apache.org/jira
Hi All,
It seems that that post is closest one to the subject I want to ask.
I use WS-addressing with Camel-CXF component. I send a request to a web-
service (configured as to ref=cxf:bean:... endpoint).
I can see that by default the addressing header is included into my
SOAP-request. My task
.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages-tp4370106p4373076.html
Sent from the Camel - Users mailing list archive at Nabble.com.
to create a response message but
since it is a one-way method, no response exists.
I believe this is just a warning so it might simply be advisory, but did I
configure WS addressing incorrectly?
Thanks,
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS
/ReplyTo
/soap:Header
soap:Body/
/soap:Envelope
Since this is a one-way method and annotated as such, I am wondering why
there is a reply. Any ideas?
Thanks,
Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-with-WS-Addressing-and-one-way-messages
org.apache.camel.processor.Logger log
I know what AmbiguousMethodCallException means, but I can't tell why it is
raised.
What am I doing wrong ?
Regards.
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component-testing-tp3400123p3400123.html
Sent from the Camel - Users mailing list
)
at java.lang.Thread.run(Thread.java:662)
Feb 25, 2011 2:09:49 PM org.apache.camel.processor.Logger log
I know what AmbiguousMethodCallException means, but I can't tell why it is
raised.
What am I doing wrong ?
Regards.
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-component
I also updated the OSGi meta data of camel-cxf for this requirement.
Willem
William Tam wrote:
I just want to point it out (as noted in the release wiki page). As the
result of CAMEL-2614, we has eliminated custom CXF interceptors that
parse message in PAYLOAD mode will require CXF 2.2.8.
this
way?
--
View this message in context:
http://www.nabble.com/CXFSpringEndpoint-and-CXFSpringEndpointBean-in-camel-cxf-component-tp24275329p24275329.html
Sent from the Camel - Users mailing list archive at Nabble.com.
CxfEndpoint can work without Spring. Camel-cxf component
provider/customer etc operates on CxfEndpoint (not CxfSpringEndpoint)
as it does not assume the use of Spring. CxfSpringEndpoint extends
CxfEndpoint and overrides some methods to use Spring. And, pretty
much every endpoint in Camel
Hi Folks,
As per the release notes seems like the camel cxf component has been
refactored a lot in the 2.0 M2 release, but the documentation that can be
found in http://camel.apache.org/cxf.html is not updated (because of which I
wasted one whole day figuring out what is going on). Am posting
of not checking the release notes
:( .
One humble request to the people who ever is maintaining the documentation,
to please put a note there on the cxf component documentation that Its not
updated as per M2 release or something of that sort.
Things am talking about is Headers section of cxfbean
org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptor
handleMessage
INFO: class
org.apache.cxf.binding.soap.interceptor.Soap12FaultOutInterceptorapplication/soap+xml
--
View this message in context:
http://www.nabble.com/Camel--CXF-Component-tp23845875p23845875.html
Sent from the Camel - Users mailing list archive at Nabble.com.
1 - 100 of 104 matches
Mail list logo
