,
William
On 05/05/2010 08:28 PM, Willem Jiang wrote:
There is a CXF related issue[1] need CXF 2.2.8.
It could be great if we release Camel 2.2.3 after CXF 2.2.8.
[1] https://issues.apache.org/activemq/browse/CAMEL-2614
Willem
William Tam wrote:
+1
On 05/05/2010 12:28 PM, Christian Schneider
You need to configure CXF client conduit to use basic authentication as
described in the wiki below. The conduit name is the WSDL port name
appended with ".http-conduit" (as mentioned in the wiki).
https://cwiki.apache.org/CXF20DOC/client-http-transport-including-ssl-support.html
On 05/13/20
It is fine to create a property for default operation to be invoke
On 06/02/2010 12:00 AM, Claus Ibsen wrote:
On Tue, Jun 1, 2010 at 8:40 PM, Jon Anstey wrote:
You just have to set the operationName header before invoking the CXF
endpoint. Something like this if you want to do this withi
There is a way of adding the XML header by using JAXWS handler.
http://stackoverflow.com/questions/1614431/webservicice-with-apache-cxf-and-custom-headers
But, let me see if there is a easier way to it without requiring handler.
On 06/21/2010 11:50 AM, S. Ali Tokmen wrote:
Hello
I have ro
I have no luck finding another way. You can try posting in the CXF
forum if the handler way does not work for you.
On 06/22/2010 12:20 PM, William Tam wrote:
There is a way of adding the XML header by using JAXWS handler.
http://stackoverflow.com/questions/1614431/webservicice-with-apache
ache/camel/component/cxf/WriteXmlDeclarationInterceptor.java
[3]https://issues.apache.org/activemq/browse/CAMEL-2841
Willem
--
Apache Camel, Apache CXF committer
Open SOA http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/wille
If it is possible to use Spring to create the route, you can name the
cxfendpoint beans differently.
On 07/26/2010 05:35 AM, Willem Jiang wrote:
Maybe CxfEndpoint didn't take the DataFormat parameter into account
when it build the Endpoint URI :(
Willem
Claus Ibsen wrote:
On Mon, Jul 26,
Willem and I would like to start a discussion regarding which release of
Camel should be upgraded to CXF 2.3. There is a lot of good reasons to
upgrade to CXF 2.3. However, upgrading it in Camel 2.6 could mean
stopping supporting CXF 2.2.x in the future Camel 2.x releases. (see
https://is
Mixing of POJO and PAYLOAD is probably fine but you have to do some
conversion (e.g. in a processor). You know the message body for POJO
mode is List and for PAYLOAD mode is CxfPayload. So, it needs
conversion from a List to CxfPayload for the request and convert
back from CxfPayload to List
I think you need to set the mode back to PAYLOAD mode inside the second
processor (convertResponse) until CAMEL-3420 is fixed and delivered. I
added a unit test for your reference.
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/Cx
We do have an unit test for JAXWS handler in PAYLOAD mode.
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/CxfWsdlFirstPayloadModeTest.java
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/resources/org/apac
On 12/14/2010 08:51 AM, ext2 wrote:
> Hi:
>
> The cxf component (payload model)will wrapped the soap message in a
> CXFPayLoad or a CXFMessage. Both are not advantage for camel's script
> language to access headers and body xml。
> I cannot use a simple expression etc: simple language
OAP header by simple("${body.headers[2]")
In all cases, an Element is returned but you can easily convert it to a
string if you like.
On 12/14/2010 10:09 AM, William Tam wrote:
>
> On 12/14/2010 08:51 AM, ext2 wrote:
>> Hi:
>>
>> The cxf component (payload model
e to use
> camel as web service mediator"?
> Or camel cannot act as a better mediator for webservice?
>
> original-
> Sender: William Tam [mailto:email.w...@gmail.com]
> Date: 2010/12/14 23:10
> Receiver: users@camel.apache.org
> Subject: Re: Questions of how to
I think you have to provide a serviceClass in this case. The
serviceClass is only retrospected to create a CXF service endpoint.
Yes, If you specific PAYLOAD mode, the XML message unmarshalling to Java
will not be performed by the Camel-cxf endpoint.
It's looks you are using the simple fro
On CXF side, you can access headers like this:
import org.apache.cxf.message.Message;
Message cxfMessage;
Map> cxfHeaders =
(Map)cxfMessage.get(Message.PROTOCOL_HEADERS);
List values = cxfHeaders.get("myheader");
On 12/23/2010 09:54 AM, Aki Yoshida wrote:
Hi,
I am trying to pass the Camel
Hi Aki,
If you need to send arbitrary payload to some target servcie, you may
consider using Camel HTTP component. Camel CXF component uses
ClientFactoryBean APIs (including message mode) which is subject to the
limitation you observed.
Regards,
William
On 02/15/2011 07:49 AM, Aki Yoshida
ture
integrated in CxfProducer/CxfEndpoint.
I would like to experiment with this idea. If you have some suggestion
that would be appreciated.
Thanks.
Regards, Aki
On Tue, Feb 15, 2011 at 5:19 PM, William Tam wrote:
Hi Aki,
If you need to send arbitrary payload to some target servcie, you may
ave arbitrary generic CXF interceptors to be placed
just as for the normal case. So, I don't think Camel DSL or processor
can fit into this picture.
Regards, aki
On Tue, Feb 15, 2011 at 7:56 PM, William Tam wrote:
What does your CXF interceptor do? You know you have Camel DSL or
processor in your ar
.org/confluence/display/CAMEL/CXF
On 02/16/2011 10:01 AM, William Tam wrote:
Hi Aki,
I am not sure I am following your intent. If a typed CXF endpoint is
needed, shouldn't a WSDL or service class is needed to define the
"type"/interface? If it has neither the CXF endpoint is no
I am proposing to replace component local header
"CamelCxfBeanRequestBasePath" in cxfbean by a new header
"CamelHttpBaseUri" to be defined in Exchange.java. That can improve
interoperability between components that deal with HTTP/REST. Let me
know if there is any concerns. Thx.
- William
In
In POJO mode, the SOAP headers are copied to Camel IN headers as
"org.apache.cxf.headers.Headers.list." The header value is a List of
CXF Header objects
(http://svn.apache.org/repos/asf/cxf/trunk/api/src/main/java/org/apache/cxf/headers/Header.java).
That's how you can read request SOAP headers.
Are you using 2.x? (My reply was assuming you were using 2.x).
On Tue, Aug 25, 2009 at 10:16 AM, William Tam wrote:
> In POJO mode, the SOAP headers are copied to Camel IN headers as
> "org.apache.cxf.headers.Headers.list." The header value is a List of
> CXF Hea
body =
(org.apache.camel.component.cxf.CxfMessage)in.getBody();
org.apache.cxf.message.Message cxfMessage = body.getMessage();
List soapHeaders =
cxfMessage.get(org.apache.cxf.headers.Header.Header.HEADER_LIST);
On Tue, Aug 25, 2009 at 10:18 AM, William Tam wrote:
> Are you using 2.x? (My reply was
wrote:
> On Tue, Aug 25, 2009 at 4:38 PM, William Tam wrote:
>> In 1.x, we don't copy the Headers.list to Camel headers. You can get
>> the Headers.list by first getting the CXF Message from Camel Message.
>> And then, you can get the header list from CXF message.
>>
Just took a peek at the doc. The PAYLOAD mode doc in that area needs
improvement, too. I will look into it.
On Tue, Aug 25, 2009 at 11:01 AM, William Tam wrote:
> Will do, Claus. :-) Getting SOAP headers and body have been
> documented for PAYLOAD mode (both 1.x and 2.x). For MESSAG
Hi Todd and Willem,
Willem's suggestion would work. We do support multiple URI templates
on a same route.
So, you could do something like: (also see
http://cwiki.apache.org/confluence/display/CAMEL/Restlet)
/blah.com/people/{id}
/blah.com/people/{id}.json
from("restlet:http:
b wrote:
>
> Hi,
>
> Sorry for the late response on this from my side, we could able to get the
> headers from the exchange but the problem that we are facing was how to set
> the headers on out message? Any sample code?
>
> Thanks,
> Trivedi
>
>
> William Tam
y of camel message is a CxfPayload object. You can
call CxfPayload.getHeaders() to get a List of SOAP headers.
To set you response, you just set your CxfPayload object in out body
of the exchange.
On Thu, Aug 27, 2009 at 12:06 AM, William Tam wrote:
> What version of Camel are you running? I
It sounds good to me.
On Sun, Aug 30, 2009 at 3:13 AM, Claus Ibsen wrote:
> On Fri, Aug 28, 2009 at 8:43 AM, Gert-Jan van de
> Streek wrote:
>>
>> I would recommend adding "transfer-encoding" to the out filter in
>> HttpHeaderStrategy.
>>
>> When for example "transfer-encoding: chunked" is acciden
Hi Trivedi, I'll try to get that today.
On Fri, Aug 28, 2009 at 3:26 PM, trivedi kumar
b wrote:
>
> Hi William,
>
> I am using Camel 1.x, can you provide me a sample how to set headers in
> Exchange for POJO based CXF webservices?
>
> Thanks,
> Trivedi
>
> Willi
Sorry, i've been quite busy. I'll get to it today.
On Wed, Sep 2, 2009 at 3:12 AM, trivedi kumar b wrote:
>
> Hi,
>
> Did you get a chance to look into this?
>
> Thanks,
> Trivedi
>
>
> William Tam wrote:
>>
>> Hi Trivedi, I'll try
. InsertRequestOutHeaderProcessor does
not require any fixes.
Cheers,
William
On Wed, Sep 2, 2009 at 9:10 AM, William Tam wrote:
> Sorry, i've been quite busy. I'll get to it today.
>
> On Wed, Sep 2, 2009 at 3:12 AM, trivedi kumar b
> wrote:
>>
>> Hi,
>>
>> Did yo
Hi Shailesh,
Could you file a Jira with a test case? Also, are you running in
POJO mode as well?
Thanks,
William
On Thu, Sep 3, 2009 at 11:17 AM, nero_s wrote:
>
> Hi William,
> I am facing some issues with WS-Adressing headers. The incoming headers are
> being simply echoed back, instead of m
age = exchange.getIn().getBody(CxfMessage.class);
I will update the test and just want to be aware of it.
Thanks,
William
On Thu, Sep 3, 2009 at 12:27 AM, William Tam wrote:
> Hi Trivedi,
>
> You can now find some samples in this test module:
> https://svn.apache.org/repos/asf/camel/branche
llowing code and it is
> displaying perfectly fine.
>
> exchange.getOut().setBody(subscribeResponse);
>
> Please help me to also set the SoapHeaders in the response, so that they are
> visible in SoapUI along with the body.
>
> Thanks for your help.
>
> Regards,
> K
On Mon, Sep 7, 2009 at 9:15 AM, William Tam wrote:
> Hi Kavita,
>
> ResponseContext map is a CXF implementation detail. CXF client puts
> information related to a response in that map. The map is eventually
> copied to the CXF response message.
>
I shouldn't say it
MEL-1994
>
> And yes, the endpoint has been configured with POJO DataFormat.
>
> Thanks,
> Shailesh.
>
>
>
>
> William Tam wrote:
>>
>> Hi Shailesh,
>>
>> Could you file a Jira with a test case? Also, are you running in
>> POJO mode as we
t; //newHeader.setMustUnderstand(false);
>
> soapHeaders.add(newHeader);
>
> When I do a debug, I can see the new header's value in the soapHeaders list.
> But no headers are being displayed in the SoapUI response message.
>
> What "extra" I need to do to b
I probably won't be able to get to it this week. If anybody wants to
work on it before then, please feel free (and update the Jira status).
On Mon, Sep 7, 2009 at 10:27 PM, William Tam wrote:
> Hi Shailesh,
>
> Thanks for the testcase. I'll take a look.
>
> Regards,
&g
Thanks Max, for the investigating the issue and posting back the outcome.
Max Ferrari wrote:
Apologies,
I skipped the part where it says
"converting %hh hex-escaped characters to their ASCII equivalents".
Indeed this is a client issue (third party).
2009/12/11 Max Ferrari :
From RFC2111
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
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
?
If you are using PAYLOAD DataFormat, I'm afraid you need to use
Latest Camel 2.3.0 SNAPSHOT. As William Tam just added a
enhancement for it[1]
[1]https://issues.apache.org/activemq/browse/CAMEL-2495
HiS wrote:
Hi All,
We are using CXF 2.2.3 with Camel 2.0.0 for exposing an end-point on
Tomcat
BTW, CAMEL-2544 and CAMEL-2495 are issues for throwing Application SOAP
Fault when the CXF endpoint is in PAYLOAD mode and no SEI (serviceClass)
is provided.
William Tam wrote:
I think it is hard to workaround the problem. If you can rebuild
just the camel-cxf component yourself, you can
Have you tried setting the Content-Type header (to "application/json")
in your request Camel message? It looks like
DefaultRestletBinding.populateRestletRequestFromExchange() method will
add the header to the Form. If it does not work, any chance you are
create a Jira with a testcase? A patc
ch is hard coded to use
'application/x-www-form-urlencoded'.
I will look into creating a jira issue and a test case, and possibly provide
a fix as well.
Rich
William Tam wrote:
Have you tried setting the Content-Type header (to "application/json")
in your request Camel
Yea, agreed with lacking documentation on this component. (I guess
contribution is always welcomed :-))
On the NoSuchMethodError, javadoc says, "Normally, this error is
caught by the compiler; this error can only occur at run time if the
definition of a class has incompatibly changed." So, are
Hi,
I submitted a fix in the trunk. Please get it a try. It hasn't been
merged to the 1.x branch yet.
w...@lenw500:~/repos/apache/camel/trunk/components/camel-restlet$ svn
ci -m "[CAMEL-1284] Restlet binding does not properly insert/extract
Restlet message."
Sendingcamel-restlet/pom.xm
Hi Liav,
If you are using Camel fuse-1.4.0.0, the addInterceptStrategy() method
does not yet exist in CamelContext. Try a newer version. It should
be there in fuse-1.4.1.0.
http://projects.open.iona.com/projects/svn/iona/camel/tags/camel-1.4.0.0-fuse/camel-core/src/main/java/org/apache/camel/Ca
The stack does not match the current source. (It points to the old
CxfProducer before refactoring.) Could you compile manually and
re-test it?
Any idea why the 2.0 snapshot is more than a week old, anyone?
On Fri, Jan 23, 2009 at 10:44 AM, S. Ali Tokmen
wrote:
> Hello
>
> Unfortunately, Cam
org.apache.camel.Component and org.apache.camel.Endpoint interfaces
are not generic in 2.0 is expected. it is a clean up effort in 2.0.
On Fri, Jan 23, 2009 at 12:01 PM, William Tam wrote:
> The stack does not match the current source. (It points to the old
> CxfProducer before refac
el-cxf/src/test/java/org/apache/camel/component/cxf/spring/CxfEndpointBeanWithBusTest.java
Adding
camel-cxf/src/test/resources/org/apache/camel/component/cxf/spring/CxfEndpointBeansRouterWithBus.xml
Transmitting file data ...
Committed revision 737122.
On Fri, Jan 23, 2009 at 12:03 PM, W
Let me ask a dumb question. What is the benefit of doing this?
What's wrong with using "from" URI "cxf:bean:" and let the
CxfComponent construct the endpoint? I thought endpoint was always
created by a component(?) Why we want to bypass all of that? Now, I
think the CxfEndpoint may have a null c
Jan 24, 2009 at 10:45 AM, William Tam wrote:
> Let me ask a dumb question. What is the benefit of doing this?
> What's wrong with using "from" URI "cxf:bean:" and let the
> CxfComponent construct the endpoint? I thought endpoint was always
> created by a
quot;ref" could be reusing an endpoint
definition in more than one route. This should achieve it.
On Sat, Jan 24, 2009 at 11:15 AM, William Tam wrote:
> In the "Ref" wiki page (http://camel.apache.org/ref.html), a sample
> usage suggests that endpoint bean is created from URI with c
nt can be created by other not just by the component :)
I guess my question was "should we".It looks like null component
is fine for CxfEndpoint.. Let's hope it won't come back to bite us.
:-)
>
> Willem
>
>
> William Tam wrote:
>> Let me a
BTW, Happy New Year!
On Sun, Jan 25, 2009 at 6:09 PM, William Tam wrote:
> On Sun, Jan 25, 2009 at 3:08 AM, Willem Jiang wrote:
>> Hi William,
>>
>> Yes, I should set the beanId when I create the CxfSpringEndpont. I just
>> committed a quick fix for it.
>
> Tha
ndpoint can be created by other not just by the component :)
>
> Willem
>
>
> William Tam wrote:
>> Let me ask a dumb question. What is the benefit of doing this?
>> What's wrong with using "from" URI "cxf:bean:" and let the
>> CxfCompone
Willem, nevermind. It's been fixed.
On Sun, Jan 25, 2009 at 11:53 PM, William Tam wrote:
> Hi Willem,
> Some cxf tests are failing due to class cast exception in
> CxfEndpointBeanDefinitionParser.doParse()
>Map map = (Map)
> bean.getBeanDefinition().getPropertyValue
That would make sense. Will get it fixed. Thanks for your patch.
https://issues.apache.org/activemq/browse/CAMEL-1312
On Tue, Feb 3, 2009 at 5:16 PM, nojonojo wrote:
>
> I'll go so far as to suggest a change that would enable both of these. In
> the DefaultRestletBinding class, the populateR
Fix has been committed to trunk and 1.5.x branch.
On Tue, Feb 3, 2009 at 6:00 PM, William Tam wrote:
> That would make sense. Will get it fixed. Thanks for your patch.
> https://issues.apache.org/activemq/browse/CAMEL-1312
>
>
> On Tue, Feb 3, 2009 at 5:16 PM, nojonojo wrote
Hi Nolan, thanks for your suggestion. I've submitted a fix.
camel-1.x: Committed revision 742855.
2.0 trunk: Committed revision 742854.
[Camel-1329].
On Mon, Feb 9, 2009 at 5:14 PM, nojonojo wrote:
>
>
> It looks like parameters sent in the query string of a request processed by
> the restlet co
Hi Todd,
Thanks for your feedback. Fault handler of Restlet component should
be consistent with other components. It sounds like it isn't. Let
me look into it.
Cheers,
William
On Mon, Feb 23, 2009 at 7:21 PM, tfredrich wrote:
>
> I'm utilizing the Restlet component (via a Trunk build) and a
I submitted a fix. Restlet component now checks for
Exchange.isFailed() and looks at Fault message to prepare a response
when isFailed() is true. It is consistent with HTTP component.
https://issues.apache.org/activemq/browse/CAMEL-1400
On Thu, Feb 26, 2009 at 10:55 AM, William Tam wrote
Hi Todd,
I submitted a fix which is along the same line as your proposed
change. I believe it should work in your case. Let me know it goes.
Thanks.
Cheers,
William
On Fri, Feb 27, 2009 at 10:48 AM, tfredrich wrote:
>
> A proposed change to DefaultRestletBinding is attached. This patch wor
Hi Todd,
I don't think Restlet component supports FileUploader extension
currently. As always, contribution is welcomed. Please submit a
Jira (and perhaps, a patch) :-)
Cheers,
William
On Fri, Feb 27, 2009 at 12:10 PM, tfredrich wrote:
>
> Does the Restlet component handle file uploading?
I'm looking into it.
https://issues.apache.org/activemq/browse/CAMEL-1416
On Tue, Mar 3, 2009 at 12:08 PM, Claus Ibsen wrote:
> Hi
>
> Looks like the # reference failed.
> serviceClass="#reportIncidentEndpoint"
>
> eg # instructs Camel / CXF to lookup in Spring for a bean with that
I submitted a fix (Committed revision 749772). Let me know if you see
other issues. Thanks.
Cheers,
William
On Tue, Mar 3, 2009 at 3:36 PM, William Tam wrote:
> I'm looking into it.
>
> https://issues.apache.org/activemq/browse/CAMEL-1416
>
>
> On Tue, Mar 3, 2009 a
I think you hit a bug that CxfEndpointBean's bean property map not
getting merged. I'll look into it.
On Wed, Mar 4, 2009 at 10:57 AM, cmoulliard wrote:
>
> In fact, I think that I don't use the correct syntax. Here is the good one :
>
>
> address="http://localhost:80
I just submitted a fix to trunk (Committed revision 750147). BTW, you
could also define dataFormat in the endpoint URI (e.g.
cxf:bean:reportIncident?dataFormat=PAYLOAD).
https://issues.apache.org/activemq/browse/CAMEL-1421
On Wed, Mar 4, 2009 at 2:13 PM, William Tam wrote:
> I think you hi
Hi Todd,
Your usecase seems to justify use of camel-restlet. For example, user
code will need to deal with RESTful URI and authentication if it is
using camel-jetty. I'll create a Jira to support multipart message.
Cheers,
William
On Tue, Mar 3, 2009 at 5:53 PM, tfredrich wrote:
>
> As usual,
Patch have been applied to trunk and 1.x branch. Thanks.
On Thu, Mar 12, 2009 at 1:28 PM, Claus Ibsen wrote:
> On Thu, Mar 12, 2009 at 6:24 PM, nojonojo wrote:
>>
>> It appears to me that the Restlet component doesn't support character sets
>> other than the default. In general, Camel uses the
Hi,
I think the DATA_FORMAT property in the exchange was not intended to
be used outside CXF component before. In 1.x, the DATA_FORMAT was
only set by the CXF producer and not by the consumer. So, if we are
going to make it "public", we should set it in both side to be useful.
I agree that 2.
https://issues.apache.org/activemq/browse/CAMEL-1476
On Sun, Mar 22, 2009 at 10:29 AM, William Tam wrote:
> Hi,
>
> I think the DATA_FORMAT property in the exchange was not intended to
> be used outside CXF component before. In 1.x, the DATA_FORMAT was
> only set by the CXF p
the Camel 2.0 syntax to specify the data
> format name? Like this
> String DATA_FORMAT_PROPERTY = "CamelCXFDataFormat";
> It is because we use it in Camel, and it could make Exchange property
> JMS friendly.
>
> And We keep use the constant of DATA_FORMAT_PROPERTY in Camel
; what was needed to provide a CamelCXFDataFormat property on the camel
> exchange, on the consumer side. I will try to setup a test case tomorrow to
> verify the fix.
>
> -Mike
>
> -Original Message-
> From: William Tam [mailto:email.w...@gmail.com]
> Sent:
That's strange. The APIs didn't change (looking at camel-1.5.1-fuse)
. The getMessage() method is still there.
On Fri, Mar 27, 2009 at 11:35 AM, mario_horny wrote:
>
> Hi guys,
>
> I'm using camel 1.5.1.1 coming with artix 5.5.
>
> I was trying to get back to a code snipped that Willem has prov
Hi Bharath,
Yes, it is possible to use Camel as Conduit and Destination of CXF.
You can find more information on this page:
http://cwiki.apache.org/confluence/display/CAMEL/CXF+Example. See
the section "CXF example for using Camel transport". Essentially, a
custom transport for CXF has been wr
On Thu, Apr 16, 2009 at 10:04 AM, William Tam wrote:
> Hi Bharath,
>
> Yes, it is possible to use Camel as Conduit and Destination of CXF.
> You can find more information on this page:
> http://cwiki.apache.org/confluence/display/CAMEL/CXF+Example. See
> the section "CXF
Hi Katta,
Thanks for your helpful feedback. Whoever refactored http header
names have forgotten to update wiki. I'll update the page.
Cheers,
William
On Fri, Jun 26, 2009 at 11:02 AM, Srivatsa Katta wrote:
>
> Hi Folks,
>
> As per the release notes seems like the camel cxf component has been
It sounds like a bug. I'll take a look. Thanks.
On Mon, Jun 29, 2009 at 2:33 PM, Srivatsa Katta wrote:
>
> Hi,
>
> Am having a jetty endpoint which has been backed by the CXF bean processor,
> am using jax-rs compatible cxfbean component. It absolutely works fine in
> happy path scenarios, but
A fix has been submitted to the trunk.
https://issues.apache.org/activemq/browse/CAMEL-1774
Thanks,
William
On Mon, Jun 29, 2009 at 8:12 PM, William Tam wrote:
> It sounds like a bug. I'll take a look. Thanks.
>
> On Mon, Jun 29, 2009 at 2:33 PM, Srivatsa Katta wrote:
>
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 extends
> 1)What use cases is the WSDLSoapServiceFactoryBean used for? (Yes I have
> looked at call hierarchy in eclipse)?
WSDLSoapServiceFactoryBean is exclusively used by CXF Soap component
(with scheme "soap") which is a component lives in camel-cxf that only
uses CXF SOAP binding not CXF transports.
Here is a way to do it. I think you can structure your routes (one
route per branch) to make it simpler to use JMX to monitor activities
each branch.
.when(header(CxfConstants.OPERATION_NAME).isEqualTo("getFoo"))
.to("direct:getFooBranch")
.when(header(CxfConstants.OPERATION_NAME).isEqualT
I believe you can set the CamelDestinationOverrideUrl header to
override the target service URL. It works for both SOAP (camel-cxf)
and REST (camel-cxfrrs).
On Wed, Feb 13, 2013 at 10:45 AM, jdev.hari wrote:
> Hi,
>
> I define my end point in camel context xml and during runtime I override
> th
Hi Aki,
I recalled my suggestion was to try passing a dummy class in the
cxfEndpoint config. It should allow you to send arbitrary payload. I
guess that didn't work? It looks like your patch is doing just that am
I missing something.
I.e.
http://localhost:9000/SoapContext/MyPort";
t the endpoint setup.
Another reason for this setup was to hide this ugly DummyImpl name
from the spring configuraiton and make the configuraiton look simpler.
Thanks.
Regards, Aki
2011/3/11 William Tam:
Hi Aki,
I recalled my suggestion was to try passing a dummy class in the cxfEndpoint
config.
p the camel-cxf producer to the Dispatch
module also.
3. As we are doing the Camel 2.7.0 release now, I suppose we apply
this patch after the Camel 2.7.0 released to give us some time for
testing this new feature.
Willem
On 3/11/11 10:23 PM, William Tam wrote:
Thanks Aki. I'll take a clos
If your processor is doing something like below, the only thing I can
think of is PAYLOAD mode was not specified properly. You can raise the
log level to DEBUG or TRACE to see what is going on.
public void process(final Exchange exchange)throws Exception {
...
I think if your route is below, the query "locale=cs_CZ" will be added
to the actual GET request's query string (but not the "reserved"
queries/options as documented in the wiki such as CamelHttpMethod).
from("direct:test").to("restlet:http://localhost:8089?locale=cs_CZ&CamelHttpMethod=GET";)
RE: Setting request query string at runtime
We can enhance camel-restlet component so that it can read Camel message
header "CamelHttpQuery" and set its value in the request URI. I can
look into that. If you'd like to submit a patch, it would be appreciated.
RE: Custom headers not getting in
The issue with setting queries in the request URI has been resolved.
Please see https://issues.apache.org/jira/browse/CAMEL-3808
Regards.
On 03/18/2011 10:18 AM, mat127 wrote:
Hello,
I am using the camel-restlet component to build a REST client calling some
3rd party application RESTful AP
Hi Andrei,
cxf:bean is not required. The producer in cxf uri should work as you
expected. There is quite a few of unit tests that cover producer uri
expressed in just "cxf".
Here is one example.
https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/cam
Andrei,
If you do not specify both service class and WSDL in the endpoint, the
validation is bypassed. (The "skipPayloadMessagePartCheck" flag is not
a user settable option). You can send any XML payload you wish.
Otherwise, message will be checked to make sure required body parts are
prov
.
So, no problems with it.
Regards,
Andrei.
-Original Message-
From: William Tam [mailto:email.w...@gmail.com]
Sent: 02 October 2011 16:55
To: users@camel.apache.org
Subject: Re: Camel CXF generic producer before 2.8.0
Andrei,
If you do not specify both service class and WSDL in the endpoint, th
I opened a Jira https://issues.apache.org/jira/browse/CAMEL-5268 to
track this issue.
Thanks.
On 05/08/2012 03:47 AM, pchakinala wrote:
Hi ,
We have restful service developed with CXF. Now we are planning to consume
it using camel-restlet component. We are setting below headers to return
res
98 matches
Mail list logo
