Re: Camel CSV Component Not Outputting Headers Correctly
Figured it out. The lastName key needed to be the correct case (lastName instead of lastname). -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CSV-Component-Not-Outputting-Headers-Correctly-tp5761848p5761927.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Removing a route after it is completed
Thank you. Since I am using akka, I need to kill that actor as well to stop it totally. -- View this message in context: http://camel.465427.n5.nabble.com/Removing-a-route-after-it-is-completed-tp5761836p5761929.html Sent from the Camel - Users mailing list archive at Nabble.com.
Camel 2.14.2 version
Hi, When is Camel 2.14.2 is due for release? Thanks, KP
Re: Camel Hawtio route diagram
Thanks Guys! You gave me some ideas to try -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Hawtio-route-diagram-tp5761803p5761928.html Sent from the Camel - Users mailing list archive at Nabble.com.
how to run a consumer route once?
I've used timer, but time manage not to work with a consumer endpoint. The header/body end up being empty. from:timer?repeatCount=1 to:quot;file://fromDirectoryquot; to:quot;file://toDirectoryquot; that doesn't work since I am trying to consumer after the timer. thanks -- View this message in context: http://camel.465427.n5.nabble.com/how-to-run-a-consumer-route-once-tp5761932.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Enabling CXF's LoggingOutInterceptor in Payload mode
Hi Aki, I didnt get any exception .I was missing the output in the operation parameter in the wsdl, When I add the output , LoggingOutInterceptor is invkoed in payload mode. I think payload and message modes acts in diffrent intercepotor chain phases. Thanks, Mahesh - Thanks And regards, Mahesh -- View this message in context: http://camel.465427.n5.nabble.com/Enabling-CXF-s-LoggingOutInterceptor-in-Payload-mode-tp5761872p5761931.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel CSV Component Not Outputting Headers Correctly
Thank you Minh. I'm actually not using Bindy; however, your comment is helpful. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-CSV-Component-Not-Outputting-Headers-Correctly-tp5761848p5761926.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Enabling CXF's LoggingOutInterceptor in Payload mode
HI reji, Its not working for me in that way . Try to exceute the secenario once. Please refer camel documet http://camel.apache.org/cxf.html. Thanks, Mahesh - Thanks And regards, Mahesh -- View this message in context: http://camel.465427.n5.nabble.com/Enabling-CXF-s-LoggingOutInterceptor-in-Payload-mode-tp5761872p5761930.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: how to run a consumer route once?
The file component has a build in timer. You don't need the first line. from:quot;file:// fromDirectoryquot; to:quot;file://toDirectoryquot; I'm not sure if you really want to read only once from the file system. If yes, you should probably think about an other solution... Best regards - Claus On Tue, Jan 20, 2015 at 6:16 AM, aidatechinc hfao...@aidatech.com wrote: I've used timer, but time manage not to work with a consumer endpoint. The header/body end up being empty. from:timer?repeatCount=1 to:quot;file://fromDirectoryquot; to:quot;file://toDirectoryquot; that doesn't work since I am trying to consumer after the timer. thanks -- View this message in context: http://camel.465427.n5.nabble.com/how-to-run-a-consumer-route-once-tp5761932.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel CSV Component Not Outputting Headers Correctly
Claus,
Thank you for the prompt response. I have some improvement as the results
are now ordered; however, I'm getting an additional comma in the values:
Order Number,First Name,Last Name
1003,Jane,,Smith
1004,Larry,,Horse
1005,Michael,,Tester
I put a wiretap prior to marshalling and have the following:
Exchange[ExchangePattern: InOnly, BodyType: java.util.ArrayList, Body:
[{orderNumber=Order Number, firstName=First Name, lastName=Last Name},
{orderNumber=1003, firstName=Jane, lastname=Smith}, {orderNumber=1004,
firstName=Larry, lastname=Horse}, {orderNumber=1005, firstName=Michael,
lastname=Tester}]]
I'll try to look into the code for how this is being marshalled, but again,
any help would be appreciated.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CSV-Component-Not-Outputting-Headers-Correctly-tp5761848p5761925.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Enabling CXF's LoggingOutInterceptor in Payload mode
are you getting some exception? if the logging interceptor is not invoked, it is likely that the request payload doesn't match the given wsdl and it rejected before entering the interceptor chain. And in that case, you should see some exception. 2015-01-19 13:40 GMT+01:00 vs_mahesh vsmahesh...@yahoo.co.in: Hi, I have following camel cxf configuration bean id=loggingInInterceptor class=org.apache.cxf.interceptor.LoggingInInterceptor/ bean id=logOutInterceptor class=org.apache.cxf.interceptor.LoggingOutInterceptor /bean bean id=wsLoggingOutInterceptor class=com.mycompany.poc.cxf.interceptor.WSLoggingOutInterceptor/ cxf:cxfEndpoint id=abcd address=http://localhost:9000/poc/interceptor; serviceClass=outotec.pi.eam.id85.workhourconfirmation.SIID85WorkHourConfirmationAsyncOut wsdlURL=wsdl/SI_ID85_WorkHourConfirmation_Async_OutService.wsdl cxf:inInterceptors ref bean=loggingInInterceptor/ /cxf:inInterceptors cxf:outInterceptors ref bean=logOutInterceptor/ ref bean=wsLoggingOutInterceptor/ /cxf:outInterceptors /cxf:cxfEndpoint I am getting the outbound message when I am using dataFormat =MESSAGE format. But when I put dataFormat=Payload format am not getting the outbound message . Can anyone tell me what is the reason for this ??Is it because of the Interceptor Phases? How to enable LoggingOutInterceptor in payload mode?? Thanks, Mahesh - Thanks And regards, Mahesh -- View this message in context: http://camel.465427.n5.nabble.com/Enabling-CXF-s-LoggingOutInterceptor-in-Payload-mode-tp5761872.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel + CXF + XSL Exception when creating the Soap response
the error that you get for the PAYLOAD type means your response message doesn't match the response message defined in your wsdl. So, you will need to verify this. the error that you get for the MESSAGE type is caused by your misconfiguration in your blueprint.xml. You cannot have to uri=cxf:bean:... / to return a response message to that endpoint. If you need to return a response to the original call, you need to just leave the response message in the route so that it will be returned to that from endpoint. The to endpoint in CXF is used to send a request message (and possibly to put its response message back in the route). I suppose, you are getting the URI is not absolute error because this endpoint's url is not absolute. regards, aki 2015-01-16 23:58 GMT+01:00 L F l891...@yahoo.com.invalid: Hello camel users ! I'm trying to implement a webservice as a camel route, defined using blueprint. I have the message as XML but after i create the response, CXF is not sending it back as it should. If i use dataFormar PAYLOAD, i get The PayLoad elements cannot fit with the message parts of the BindingOperation. Please check the BindingOperation and PayLoadMessage. exception, If i use dataFormat=MESSAGE i get URI is not absolute exception. I'm probably doing something wrong, but i'm unable to find out the problem, so any help is appreciated. Thanks!
Using CXF endpoint to call an NTLM protected Rest service
Hi Its not clear to me from reading the camel cxf endpoint documentation whether I can call an NTLM protected Rest service using the CXF endpoint. Any help greatly appreciated Thanks Joe -- View this message in context: http://camel.465427.n5.nabble.com/Using-CXF-endpoint-to-call-an-NTLM-protected-Rest-service-tp5761873.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Enabling CXF's LoggingOutInterceptor in Payload mode
Hi , Its resolved now. But still I need clarity between the two different modes, Payload and Message.Why the LoggingOutInterceptor is working for message mode even output is not specified in the wsdl?? Thanks, Mahesh - Thanks And regards, Mahesh -- View this message in context: http://camel.465427.n5.nabble.com/Enabling-CXF-s-LoggingOutInterceptor-in-Payload-mode-tp5761872p5761874.html Sent from the Camel - Users mailing list archive at Nabble.com.
Enabling CXF's LoggingOutInterceptor in Payload mode
Hi, I have following camel cxf configuration bean id=loggingInInterceptor class=org.apache.cxf.interceptor.LoggingInInterceptor/ bean id=logOutInterceptor class=org.apache.cxf.interceptor.LoggingOutInterceptor /bean bean id=wsLoggingOutInterceptor class=com.mycompany.poc.cxf.interceptor.WSLoggingOutInterceptor/ cxf:cxfEndpoint id=abcd address=http://localhost:9000/poc/interceptor; serviceClass=outotec.pi.eam.id85.workhourconfirmation.SIID85WorkHourConfirmationAsyncOut wsdlURL=wsdl/SI_ID85_WorkHourConfirmation_Async_OutService.wsdl cxf:inInterceptors ref bean=loggingInInterceptor/ /cxf:inInterceptors cxf:outInterceptors ref bean=logOutInterceptor/ ref bean=wsLoggingOutInterceptor/ /cxf:outInterceptors /cxf:cxfEndpoint I am getting the outbound message when I am using dataFormat =MESSAGE format. But when I put dataFormat=Payload format am not getting the outbound message . Can anyone tell me what is the reason for this ??Is it because of the Interceptor Phases? How to enable LoggingOutInterceptor in payload mode?? Thanks, Mahesh - Thanks And regards, Mahesh -- View this message in context: http://camel.465427.n5.nabble.com/Enabling-CXF-s-LoggingOutInterceptor-in-Payload-mode-tp5761872.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel + CXF + XSL Exception when creating the Soap response
Hello Aki, By removing the to uri=cxf:bean:... / step, i have a response in SoapUI. Thank you for help, i would never find out what is the problem, Regards Laji On Monday, January 19, 2015 3:51 PM, Aki Yoshida elak...@gmail.com wrote: the error that you get for the PAYLOAD type means your response message doesn't match the response message defined in your wsdl. So, you will need to verify this. the error that you get for the MESSAGE type is caused by your misconfiguration in your blueprint.xml. You cannot have to uri=cxf:bean:... / to return a response message to that endpoint. If you need to return a response to the original call, you need to just leave the response message in the route so that it will be returned to that from endpoint. The to endpoint in CXF is used to send a request message (and possibly to put its response message back in the route). I suppose, you are getting the URI is not absolute error because this endpoint's url is not absolute. regards, aki 2015-01-16 23:58 GMT+01:00 L F l891...@yahoo.com.invalid: Hello camel users ! I'm trying to implement a webservice as a camel route, defined using blueprint. I have the message as XML but after i create the response, CXF is not sending it back as it should. If i use dataFormar PAYLOAD, i get The PayLoad elements cannot fit with the message parts of the BindingOperation. Please check the BindingOperation and PayLoadMessage. exception, If i use dataFormat=MESSAGE i get URI is not absolute exception. I'm probably doing something wrong, but i'm unable to find out the problem, so any help is appreciated. Thanks!
Re: Camel Hawtio route diagram
Hi, If you want to get the route to show you something else in the route id of the XML, you can set it manually. E.g. using the Java DSL: from(file://opt.../atg).routeId(file_consumer_atg)... Jakub On 18/01/15 04:31, aidatechinc wrote: Hello, I am using camel 2.14.1 with akka 2.3.6. I have attached the xml the hawtio is showing for a quick file consumer to a file producer. basically moving files route xmlns=http://camel.apache.org/schema/spring; id=akka://Main/user/s3_1421555118018 from uri=file:///opt/xyz/atg?delete=true/ convertBodyTo type=java.io.InputStream/ to uri=akka://Main/user/s3_1421555118018?autoAck=trueamp;replyTimeout=6 milliseconds/ /route As you can see the producer, doesn't show me that is a file component, but rather an akka actor. 1) is this a correct way to approach it? 2) or should I have once actor that spin up a routeBuilder? The ideas is I want to dynamically created routes and have akka cluster take care of the route and executed across different nodes. Provided they all have different consumer points. thank again -- View this message in context: http://camel.465427.n5.nabble.com/Camel-Hawtio-route-diagram-tp5761803p5761835.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Enabling CXF's LoggingOutInterceptor in Payload mode
Hi Mahesh The LoggingOutInterceptor will still work even if your operations doesn't have any output element as the camel route still returns back some meta informations to the soap client since default MEP is always inOut. It may include http status codes, any headers in the exchange might also get mapped and returned back to soap client as http headers and apart from these am not really sure what are the other meta informations it returns .. Cheers Reji On 19 Jan 2015 18:54, vs_mahesh vsmahesh...@yahoo.co.in wrote: Hi , Its resolved now. But still I need clarity between the two different modes, Payload and Message.Why the LoggingOutInterceptor is working for message mode even output is not specified in the wsdl?? Thanks, Mahesh - Thanks And regards, Mahesh -- View this message in context: http://camel.465427.n5.nabble.com/Enabling-CXF-s-LoggingOutInterceptor-in-Payload-mode-tp5761872p5761874.html Sent from the Camel - Users mailing list archive at Nabble.com.
simple recipientlist expansion
.recipientList(simple(direct:${body.media}))
So media is a ListString property where each entry has a media value:
sms, email, etc.
What I get out of this is an exception (where sms is the only media):
org.apache.camel.component.direct.DirectConsumerNotAvailableException: No
consumers available on endpoint: Endpoint[direct://%5Bsms%5D].
If I remove the direct: from the simple expression and place it directly in
the media property value it works fine. But then my POJO knows about
direct: prefixes. Not what I had hoped.
Any ideas? I can't use transform() as the rest of the message needs to be
passed onwards.
James
Camel-CXF: Problems transforming namespace of incoming message
Hello,
we need to build a proxy for an external request/reply SOAP web service. This
same service must be offered both unmodified (namespace A) and with a different
namespace B in the message schema. In both cases, some additional routing
decisions must be taken.
For this, we have defined a CXF producer endpoint (using cxf:cxfEndpoint) in
POJO message format that addresses the external service, using their WSDL
(namespace A). The unmodified proxy on the consuming (input) side is also a CXF
endpoint in POJO format, using the same WSDL. A route forwards (after some
routing decisions) from this to the external service; this works.
To offer the service with a different namespaces, we tried several approaches
without success.
One possibility seems to be a CXF consumer endpoint in MESSAGE message format
that uses a StaxTransformationFeature to modify the namespace from B to A.
This endpoint uses a modified WSDL with namespace B instead of A. It must use
MESSAGE, not POJO, because the WSDL file with the modified message namespace B
would not match the transformed message in namespace A, which results in a
parsing (JAXB) exception from CXF. We would like to send the transformed
message to our own namespace A consumer endpoint to run through the normal
routing decisions mentioned above. We cannot use the POJO endpoint because the
message is in MESSAGE format. So, we tried POSTing the message using the HTTP
component:
route id=cxf-admin-nsmap-route
from uri=cxf:bean:fc-admin-service/
to
uri=http://${fc.endpoint.host}:${fc.endpoint.port}/${fc.admin_cxf_nsmod.endpoint.path}/
/route
This fails with
Invalid uri: /fc/admin. If you are forwarding/bridging http endpoints, then
enable the bridgeEndpoint option on the endpoint:
Endpoint[http://$%7Bfc.endpoint.host%7D:$%7Bfc.endpoint.port%7D/$%7Bfc.admin_cxf_nsmod.endpoint.path%7D]
/fc/admin is the path for the incoming request (defined by
cxf:bean:fc-admin-service), not the one defined in the to-uri
(${fc.admin_cxf_nsmod.endpoint.path}).
We tried to add the bridgeEndpoint property as in
route id=cxf-admin-nsmap-route
from uri=cxf:bean:fc-admin-service/
to
uri=http://${fc.endpoint.host}:${fc.endpoint.port}/${fc.admin_cxf_nsmod.endpoint.path}?bridgeEndpoint=true/
/route
This fails with
org.apache.commons.httpclient.URIException: Invalid authority
A different approach where we tried XSLT to transform the namespaces, use JAXB
unmarshalling and create a MessageContentsList to convert the message into POJO
format by hand which can then be sent into the routing decision route directly
leads to difficulties with marshalling the response back: the namespace prefix
for the type names in (as xsd in xsi:type=xsd:string) gets lost. On top, this
approach seems still uglier an less maintainable than the first one I described.
What might be a working and clean, simple, maybe even elegant solution to this
problem? It's simply mapping a message in one namespace to another!
Thank you,
Dirk
Re: simple recipientlist expansion
You can use a method call expression (aka java bean) where you add the
direct: prefix to the media headers.
Or try look at groovy or something which may be able to prefix to a
list. I think I have seen that done in fabric8 v1.
On Mon, Jan 19, 2015 at 6:32 PM, James Green james.mk.gr...@gmail.com wrote:
.recipientList(simple(direct:${body.media}))
So media is a ListString property where each entry has a media value:
sms, email, etc.
What I get out of this is an exception (where sms is the only media):
org.apache.camel.component.direct.DirectConsumerNotAvailableException: No
consumers available on endpoint: Endpoint[direct://%5Bsms%5D].
If I remove the direct: from the simple expression and place it directly in
the media property value it works fine. But then my POJO knows about
direct: prefixes. Not what I had hoped.
Any ideas? I can't use transform() as the rest of the message needs to be
passed onwards.
James
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: simple recipientlist expansion
You mean a class implementing Expression?
On 19 January 2015 at 17:56, Claus Ibsen claus.ib...@gmail.com wrote:
You can use a method call expression (aka java bean) where you add the
direct: prefix to the media headers.
Or try look at groovy or something which may be able to prefix to a
list. I think I have seen that done in fabric8 v1.
On Mon, Jan 19, 2015 at 6:32 PM, James Green james.mk.gr...@gmail.com
wrote:
.recipientList(simple(direct:${body.media}))
So media is a ListString property where each entry has a media value:
sms, email, etc.
What I get out of this is an exception (where sms is the only media):
org.apache.camel.component.direct.DirectConsumerNotAvailableException: No
consumers available on endpoint: Endpoint[direct://%5Bsms%5D].
If I remove the direct: from the simple expression and place it directly
in
the media property value it works fine. But then my POJO knows about
direct: prefixes. Not what I had hoped.
Any ideas? I can't use transform() as the rest of the message needs to be
passed onwards.
James
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
hdfs2 component with kinit
Hello, I am attempting to move some files to a secure HDFS and I am getting the error: org.apache.camel.FailedToCreateProducerException: Failed to create Producer for endpoint: Endpoint[hdfs2://x..com:8020/tmp/di_pic]. Reason: org.apache.hadoop.security.AccessControlException: SIMPLE authentication is not enabled. Available:[TOKEN, KERBEROS] at org.apache.camel.impl.ProducerCache.doGetProducer(ProducerCache.java:407) ~[camel-core-2.14.0.jar:2.14.0] at org.apache.camel.impl.ProducerCache.acquireProducer(ProducerCache.java:123) ~[camel-core-2.14.0.jar:2.14.0] at org.apache.camel.processor.SendProcessor.doStart(SendProcessor.java:221) ~[camel-core-2.14.0.jar:2.14.0] is there a way to let it leverage the kinit? -- View this message in context: http://camel.465427.n5.nabble.com/hdfs2-component-with-kinit-tp5761923.html Sent from the Camel - Users mailing list archive at Nabble.com.
