Re: How to record time token after accessing a route or endpoint

[Claus Ibsen]

Camel has JMX api that offers performance metrics
http://camel.apache.org/camel-jmx.html

As an example for using the JMX any 3rd party projects/tooling can use
that for tooling purposes such as hawtio showing nice insight into
your running Camel applications
http://hawt.io/

... and there is also event notifier you can use as a programmatic way
http://camel.apache.org/eventnotifier-to-log-details-about-all-sent-exchanges.html


On Wed, Dec 4, 2013 at 8:51 AM, Ernest Lu  wrote:
> Hi,
>
> How to record time token after accessing  a route or endpoint.
>
> Thanks
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/How-to-record-time-token-after-accessing-a-route-or-endpoint-tp5744292.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
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

Re: Error in XSLT message tranformation

[madusanka]

Hi,

I changed the 2nd URI as you told. Now a FileNotFound exception is thrown.
It says "Cannot find resource in classpath for URI:
/home/madusanka/Desktop/example.xsl". The "example.xsl" file exists in my
desktop. How to set the classpath in the URI?

http://camel.apache.org/schema/spring";>








 logException in thread "SpringOsgiExtenderThread-4"
org.apache.camel.RuntimeCamelException:
org.apache.camel.FailedToCreateRouteException: Failed to create route route2
at: >>> To[xslt:///home/madusanka/Desktop/example.xsl] <<< in route:
Route[[From[file:///home/madusanka/Desktop/inbox?noop=true]]... because of
Failed to resolve endpoint: xslt:///home/madusanka/Desktop/example.xsl due
to: java.io.FileNotFoundException: Cannot find resource in classpath for
URI: /home/madusanka/Desktop/example.xsl
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1326)
at
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:120)
at
org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:285)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:303)
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:911)
at
org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
at
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
at
org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)




--
View this message in context: 
http://camel.465427.n5.nabble.com/Error-in-XSLT-message-tranformation-tp5744263p5744296.html
Sent from the Camel - Users mailing list archive at Nabble.com.

problems with route cxf -> netty

[troesler]

hello


i want to setup a camel route that has a soap webservice able to receive a
soap message and then route it towards a tcp socket. the tcp socket has to
wait for a client to connect, if its connected it then sends the message
towards it

cxf endpoint --> tcp socket (netty)


i created a cxf endpoint/webservice that normally responds to the message,
and as a test i connect a file/output endpoint to it. This worked as the
contents of the message were put into a newly created file, so far so good i
thought.
Now changing the file endpoint to netty endpoint some problems occured

1. i do testing with socket test 3, when i try to connect to that port as
client it doesnt allow me to connect (maybe because that endpoint is acting
like a client too?)

2. if i just listen on that port, i get the following message "Y sr
*org.apache.cxf.message.MessageContentsListxr
 java.util.ArrayListxp ..."

now my question

is it possible to have a soap accepting endpoint on one end and a tcp socket
on the other, that accepts connections from a client?






--
View this message in context: 
http://camel.465427.n5.nabble.com/problems-with-route-cxf-netty-tp5744294.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: problems with route cxf -> netty

[troesler]

now that i added  textline=true option to netty i get the contents readable
by listening on that port.

but now get a timeout and the problem with establishing a connection to that
port still persists.



--
View this message in context: 
http://camel.465427.n5.nabble.com/problems-with-route-cxf-netty-tp5744294p5744295.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Error in XSLT message tranformation

[Claus Ibsen]

Use file: as prefix to tell Camel its on the file system and not
classpath: which is the default

As you can see documented clearly here
http://camel.apache.org/xslt

On Wed, Dec 4, 2013 at 10:23 AM, madusanka
 wrote:
> Hi,
>
> I changed the 2nd URI as you told. Now a FileNotFound exception is thrown.
> It says "Cannot find resource in classpath for URI:
> /home/madusanka/Desktop/example.xsl". The "example.xsl" file exists in my
> desktop. How to set the classpath in the URI?
>
> http://camel.apache.org/schema/spring";>
> 
>  />
> 
>  uri="file:///home/madusanka/Desktop/outbox?noop=true"/>
> 
> 
>
>
>  logException in thread "SpringOsgiExtenderThread-4"
> org.apache.camel.RuntimeCamelException:
> org.apache.camel.FailedToCreateRouteException: Failed to create route route2
> at: >>> To[xslt:///home/madusanka/Desktop/example.xsl] <<< in route:
> Route[[From[file:///home/madusanka/Desktop/inbox?noop=true]]... because of
> Failed to resolve endpoint: xslt:///home/madusanka/Desktop/example.xsl due
> to: java.io.FileNotFoundException: Cannot find resource in classpath for
> URI: /home/madusanka/Desktop/example.xsl
> at
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1326)
> at
> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:120)
> at
> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:285)
> at
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:97)
> at
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:303)
> at
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:911)
> at
> org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
> at
> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
> at
> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Error-in-XSLT-message-tranformation-tp5744263p5744296.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
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

Re: How to run Camel with a web application

[manchandap]

haven't seen any reply to this  wondering if i need to add more information
to the original post.



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-to-run-Camel-with-a-web-application-tp5743607p5744298.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Error in XSLT message tranformation

[madusanka]

Thanks a lot. It worked. Now i want to put the XSLT file in the classpath.
Does "classpath" refer to the servicemix installation directory or the group
id (ex - org.apache.camel) in the org.apache.camel.archetype generated camel
project ? Because what I need is to put the xslt file in the camel project.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Error-in-XSLT-message-tranformation-tp5744263p5744299.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Error in XSLT message tranformation

[Claus Ibsen]

Its the classpath of your own bundle (application). If you use maven
for your development, then put the file in the src/main/resources
directory.

On Wed, Dec 4, 2013 at 10:58 AM, madusanka
 wrote:
> Thanks a lot. It worked. Now i want to put the XSLT file in the classpath.
> Does "classpath" refer to the servicemix installation directory or the group
> id (ex - org.apache.camel) in the org.apache.camel.archetype generated camel
> project ? Because what I need is to put the xslt file in the camel project.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Error-in-XSLT-message-tranformation-tp5744263p5744299.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
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

Re: How to run Camel with a web application

[Claus Ibsen]

Architectural questions is not a good fit as there is no single answer.

Camel is very flexible and you can setup how you find best for your use-cases.


On Wed, Dec 4, 2013 at 10:46 AM, manchandap  wrote:
> haven't seen any reply to this  wondering if i need to add more information
> to the original post.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/How-to-run-Camel-with-a-web-application-tp5743607p5744298.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
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

Consuming SOAP web service using Camel

[rameshbabu]

 Hi,

I am trying to consuming the soap web service using camel.

 

 // I am preparing request Object


 ;



${in.body};



  
 

 



 I am facing the following  issue.


 org.apache.camel.RuntimeCamelException:
org.apache.cxf.binding.soap.SoapFault: No namespace on "HTML" element. You
must send a SOAP request.
at
org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1157)[88:org.apache.camel.camel-core:2.8.0.fuse-07-15]
at
org.apache.camel.component.jms.EndpointMessageListener$EndpointMessageListenerAsyncCallback.done(EndpointMessageListener.java:184)[93:org.apache.camel.camel-jms:2.8.0.fuse-07-15]
at
org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:110)[93:org.apache.camel.camel-jms:2.8.0.fuse-07-15]
at
org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)[94:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)[94:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)[94:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)[94:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)[94:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)[94:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)[94:org.springframework.jms:3.0.5.RELEASE]
at
org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)[94:org.springframework.jms:3.0.5.RELEASE]
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)[:1.6.0_27]
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.6.0_27]
at java.lang.Thread.run(Thread.java:679)[:1.6.0_27]
Caused by: org.apache.cxf.binding.soap.SoapFault: No namespace on "HTML"
element. You must send a SOAP request.
at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.readVersion(ReadHeadersInterceptor.java:109)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:141)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
at
org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:780)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1678)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
at
org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream$1.run(HTTPConduit.java:1521)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
at
org.apache.cxf.workqueue.AutomaticWorkQueueImpl$2.run(AutomaticWorkQueueImpl.java:372)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
... 3 more




  







--
View this message in context: 
http://camel.465427.n5.nabble.com/Consuming-SOAP-web-service-using-Camel-tp5744305.html
Sent from the Camel - Users mailing list archive at Nabble.com.

ZeroMQ publishing infinte number of times

[harikrish07121991]

Using the following creating a dynamic ZeroMQ  route 







 

And slip function is :
public String slip(Exchange exchange)
{
log.info("publishing");
String body = exchange.getIn().getBody(String.class);
log.info("Exchange body"+body);
return 
"zeromq:tcp://0.0.0.0:5577?socketType=PUBLISH&topics=iotm/stream";
}


But the problem is the zeroMQ is publishing it infinite times the same
message.

Is it the problem with the zeroMQ URL??
Please help ..



--
View this message in context: 
http://camel.465427.n5.nabble.com/ZeroMQ-publishing-infinte-number-of-times-tp5744307.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: ZeroMQ publishing infinte number of times

[Claus Ibsen]

Read the documentation about the dynamic router eip
http://camel.apache.org/dynamic-router.html

On Wed, Dec 4, 2013 at 1:15 PM, harikrish07121991
 wrote:
> Using the following creating a dynamic ZeroMQ  route
> 
> 
> 
> 
>  />
> 
> 
>
>
> And slip function is :
> public String slip(Exchange exchange)
> {
> log.info("publishing");
> String body = exchange.getIn().getBody(String.class);
> log.info("Exchange body"+body);
> return 
> "zeromq:tcp://0.0.0.0:5577?socketType=PUBLISH&topics=iotm/stream";
> }
>
>
> But the problem is the zeroMQ is publishing it infinite times the same
> message.
>
> Is it the problem with the zeroMQ URL??
> Please help ..
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/ZeroMQ-publishing-infinte-number-of-times-tp5744307.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
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

Re: ZeroMQ publishing infinte number of times

[harikrish07121991]

Thanks for your reply Claus Ibsen-2 but you got me wrong, 
i want to create a dynamic route depending upon the data i am receiving  ..
ie each time the zmq  route changes . 




--
View this message in context: 
http://camel.465427.n5.nabble.com/ZeroMQ-publishing-infinte-number-of-times-tp5744307p5744316.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Error in XSLT message tranformation

[madusanka]

I was able to solve my problem. Thanks a lot !!!



--
View this message in context: 
http://camel.465427.n5.nabble.com/Error-in-XSLT-message-tranformation-tp5744263p5744317.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: issue with ExchangeHelper.resolveEndpoint when using RAW() parameter on authPassword

[Marco Crivellaro]

my bad, it is the same for FTP.
I got confused by another issue I've found... will open a separate thread



--
View this message in context: 
http://camel.465427.n5.nabble.com/issue-with-ExchangeHelper-resolveEndpoint-when-using-RAW-parameter-on-authPassword-tp5744246p5744320.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Method with name: sayHi not found on bean - Using apache Camel

[Arthanarisamy]

I am using apache camel to communicate to a remote EJB which is deployed in
Weblogic Server 12c. when i invoke remote EJB it throws me the below
exception org.apache.camel.component.bean.MethodNotFoundException: Method
with name: sayHi not found on bean:
ClusterableRemoteRef(3961905123449960886S:192.168.1.98:[7001,7001,-1,-1,-1,-1,-1]:weblogic:AdminServer
[3961905123449960886S:192.168.1.98:[7001,7001,-1,-1,-1,-1,-1]:weblogic:AdminServer/394])/394
of type:
com.iexceed.study.HelloRemoteEJBImpl_6zix6y_IHelloRemoteEJBImpl_12120_WLStub.
Exchange[Message: [Body is null]]

My Came-context.xml file is as below

 
 
 
 
weblogic.jndi.WLInitialContextFactory 
t3://IPADDRESS:PORT 
weblogic 
Weblogic@01 
 
http://camel.apache.org/schema/spring";>









and the java client class which i am using is

   public void postRequest(){
try {
String camelID = "camelejb";
Exchange exchange = null;
Message msg = null;
getCamelContext();
springCamelContext.start();
System.out.println("Starting camel context.");
getUriMap();
ProducerTemplate template =
springCamelContext.createProducerTemplate();
System.out.println("camelejb::" + getUriMap().get("camelejb"));
exchange = template.request(getUriMap().get(camelID), new
Processor() {

public void process(Exchange exchng) throws Exception {
   exchng.getIn().setBody("");
}
});
System.out.println("Exception:" + exchange.getException());
exchange.getException().printStackTrace();
msg = exchange.getOut();

System.out.println("Message:" + msg);
springCamelContext.stop();
System.out.println("Stopping Camel Context");
} catch (Exception ex) {
ex.printStackTrace();
}

}
EJB :

@Remote
public interface IHelloRemoteEJB {

public void sayHello(String name);

public void sayHi();
}
Having no clue why this error is thrown when the method is available in my
EJB. 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Method-with-name-sayHi-not-found-on-bean-Using-apache-Camel-tp5744319.html
Sent from the Camel - Users mailing list archive at Nabble.com.

javax.xml.transform.TransformerException

[madusanka]

Hi,

I'm trying to transform a SOAP message using XSLT. But it throws
"javax.xml.transform.TransformerException" saying Invalid encoding name. I
use SOAP 1.2. The same error was given for SOAP 1.1

2013-12-04 21:45:37,306 | ERROR | qtp27828643-221  | DefaultErrorHandler
 
| 100 - org.apache.camel.camel-core - 2.10.6 | Failed delivery for
(MessageId: ID-madusanka-G31M-40283-1386172572659-4-2 on ExchangeId:
ID-madusanka-G31M-40283-1386172572659-4-1). Exhausted after delivery
attempt: 1 caught: javax.xml.transform.TransformerException: Invalid
encoding name "http://www.w3.org/2003/05/soap-envelope";.
javax.xml.transform.TransformerException: Invalid encoding name
"http://www.w3.org/2003/05/soap-envelope";.
at
org.apache.xalan.transformer.TransformerImpl.fatalError(TransformerImpl.java:780)[:]
at
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:756)[:]
at
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1273)[:]
at
org.apache.xalan.transformer.TransformerImpl.transform(TransformerImpl.java:1251)[:]
at
org.apache.camel.builder.xml.XsltBuilder.process(XsltBuilder.java:128)[100:org.apache.camel.camel-core:2.10.6]
at
org.apache.camel.impl.ProcessorEndpoint.onExchange(ProcessorEndpoint.java:101)[100:org.apache.camel.camel-core:2.10.6]
at
org.apache.camel.component.xslt.XsltEndpoint.onExchange(XsltEndpoint.java:81)[100:org.apache.camel.camel-core:2.10.6]
at
org.apache.camel.impl.ProcessorEndpoint$1.process(ProcessorEndpoint.java:71)[100:org.apache.camel.camel-core:2.10.6]
at org.apache.camel.util.Asy



--
View this message in context: 
http://camel.465427.n5.nabble.com/javax-xml-transform-TransformerException-tp5744321.html
Sent from the Camel - Users mailing list archive at Nabble.com.

users@camel.apache.org

[Marco Crivellaro]

Hi,
there is an issue with handling password with double && even when wrapping
it into RAW() constraint

For instance the use of URI

http://hostname/script.php?authMethod=Basic&authPassword=RAW(pa&&word)&authUsername=usr

throws the exception:

org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint:
http://hostname/script.php?authMethod=Basic&authPassword=RAW(pa&&word)&authUsername=usr
due to: Invalid uri syntax: Double && marker found. Check the uri and remove
the duplicate & marker.


I am using camel 2.12.1




--
View this message in context: 
http://camel.465427.n5.nabble.com/Issue-with-password-having-double-tp5744323.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: javax.xml.transform.TransformerException

[madusanka]

the problem is with the encoding. It works properly when "UTF-8" is used



--
View this message in context: 
http://camel.465427.n5.nabble.com/javax-xml-transform-TransformerException-tp5744321p5744325.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Camel-maven-plugin 2.12.1 Problem

[atiato]

Dear Clause,

I'm have issue when running the camel project with version 2.12.1 camel
maven plugin , I rolled back to 2.9.0 to make the project work , attached is
the error log when using 2.12.1.

Thanks,
Omar Atia mavenplugin2.12.1exception.rar

  



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-maven-plugin-2-12-1-Problem-tp5744328.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Consuming SOAP web service using Camel

[Christian Posta]

what ends up being in the body (in.body)?

On Wed, Dec 4, 2013 at 3:45 AM, rameshbabu  wrote:
>  Hi,
>
> I am trying to consuming the soap web service using camel.
>
>  
> 
>  // I am preparing request Object
> 
> 
>  
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>
> xmlns:ser="http://www.sstdomain.com/service/">;
> 
> 
>
> ${in.body};
> 
> 
> 
>   
> 
>
> 
> 
>
>
>  I am facing the following  issue.
>
>
>  org.apache.camel.RuntimeCamelException:
> org.apache.cxf.binding.soap.SoapFault: No namespace on "HTML" element. You
> must send a SOAP request.
> at
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1157)[88:org.apache.camel.camel-core:2.8.0.fuse-07-15]
> at
> org.apache.camel.component.jms.EndpointMessageListener$EndpointMessageListenerAsyncCallback.done(EndpointMessageListener.java:184)[93:org.apache.camel.camel-jms:2.8.0.fuse-07-15]
> at
> org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:110)[93:org.apache.camel.camel-jms:2.8.0.fuse-07-15]
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)[94:org.springframework.jms:3.0.5.RELEASE]
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)[:1.6.0_27]
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.6.0_27]
> at java.lang.Thread.run(Thread.java:679)[:1.6.0_27]
> Caused by: org.apache.cxf.binding.soap.SoapFault: No namespace on "HTML"
> element. You must send a SOAP request.
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.readVersion(ReadHeadersInterceptor.java:109)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:141)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
> org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:780)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1678)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream$1.run(HTTPConduit.java:1521)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl$2.run(AutomaticWorkQueueImpl.java:372)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> ... 3 more
>
>
>
>
>
>
>
>
>
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Consuming-SOAP-web-service-using-Camel-tp5744305.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta

Passing parameter to Bean

[zahir]

Hello, 

I have a property file defined in applicationContext.xml

   http://camel.apache.org/schema/spring";>
 
transformation
  

there is property there in above property file names xx. I want to get its
value in bean class, but I am not able to pass it. Here is my bean class
only method:

public  String  map(String args) { ... }


I can get the property in route using {{xx}}, but not sure how to pass it to
bean.

Any advice will be appreciated.


Thank you



--
View this message in context: 
http://camel.465427.n5.nabble.com/Passing-parameter-to-Bean-tp5744331.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Consuming SOAP web service using Camel

[Willem Jiang]

What kind of CXF data format do you use?
I doubt you may put a  tag there.


Willem Jiang

Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
  http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem


On Wed, Dec 4, 2013 at 7:45 PM, rameshbabu wrote:

>  Hi,
>
> I am trying to consuming the soap web service using camel.
>
>  
> 
>  // I am preparing request Object
> 
> 
>  
> xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>
> xmlns:ser="http://www.sstdomain.com/service/">;
> 
> 
>
> ${in.body};
> 
> 
> 
>   
> 
>
> 
> 
>
>
>  I am facing the following  issue.
>
>
>  org.apache.camel.RuntimeCamelException:
> org.apache.cxf.binding.soap.SoapFault: No namespace on "HTML" element. You
> must send a SOAP request.
> at
>
> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1157)[88:org.apache.camel.camel-core:2.8.0.fuse-07-15]
> at
>
> org.apache.camel.component.jms.EndpointMessageListener$EndpointMessageListenerAsyncCallback.done(EndpointMessageListener.java:184)[93:org.apache.camel.camel-jms:2.8.0.fuse-07-15]
> at
>
> org.apache.camel.component.jms.EndpointMessageListener.onMessage(EndpointMessageListener.java:110)[93:org.apache.camel.camel-jms:2.8.0.fuse-07-15]
> at
>
> org.springframework.jms.listener.AbstractMessageListenerContainer.doInvokeListener(AbstractMessageListenerContainer.java:560)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> org.springframework.jms.listener.AbstractMessageListenerContainer.invokeListener(AbstractMessageListenerContainer.java:498)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> org.springframework.jms.listener.AbstractMessageListenerContainer.doExecuteListener(AbstractMessageListenerContainer.java:467)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.doReceiveAndExecute(AbstractPollingMessageListenerContainer.java:325)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> org.springframework.jms.listener.AbstractPollingMessageListenerContainer.receiveAndExecute(AbstractPollingMessageListenerContainer.java:263)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.invokeListener(DefaultMessageListenerContainer.java:1058)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.executeOngoingLoop(DefaultMessageListenerContainer.java:1050)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> org.springframework.jms.listener.DefaultMessageListenerContainer$AsyncMessageListenerInvoker.run(DefaultMessageListenerContainer.java:947)[94:org.springframework.jms:3.0.5.RELEASE]
> at
>
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)[:1.6.0_27]
> at
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.6.0_27]
> at java.lang.Thread.run(Thread.java:679)[:1.6.0_27]
> Caused by: org.apache.cxf.binding.soap.SoapFault: No namespace on "HTML"
> element. You must send a SOAP request.
> at
>
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.readVersion(ReadHeadersInterceptor.java:109)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
>
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:141)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
>
> org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
>
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
>
> org.apache.cxf.endpoint.ClientImpl.onMessage(ClientImpl.java:780)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
>
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseInternal(HTTPConduit.java:1678)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
>
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream$1.run(HTTPConduit.java:1521)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> at
>
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl$2.run(AutomaticWorkQueueImpl.java:372)[128:org.apache.cxf.bundle:2.4.3.fuse-04-15]
> ... 3 more
>
>
>
>
>
>
>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/C

Re: Accessing property on bean in header?

[Andrew Thorburn]

Something is broken here - not sure if it's me or Camel, but I can't
say that I expected that,given the following:

setHeader("test").simple("${in.header.simpleBean} == null",
Boolean.class).setHeader("test2").simple("${in.headers.simpleBean} !=
null", Boolean.class)

*Both* headers are false! This is using Camel 2.12.2, so the latest
version. The full output and code is here:
http://pastebin.com/xdSsatEP, and it's pretty simple, so if someone
could explain what I'm doing wrong that would be awesome.

The header, simpleBean, is definitely not null - that's confirmed in a
log message and by actually checking the header in another processor,
so I think something has gone horribly wrong in Camel... I also still
can't extract properties from header objects, so I'm assuming that's
not supported.

Thanks,

- Andrew

On Wed, Dec 4, 2013 at 8:36 PM, Andrew Thorburn  wrote:
> Yes, I did eventually figure that out, and when I did, the predicate returns
> false due to the left-hand side being converted to a String before the
> comparison takes place. Given that it's probably a bug, is it likely fixed
> in a later version of Camel? I'll try to check it myself, probably in a day
> or so.
>
> - Andrew
>
> On 4/12/2013 8:28 PM, "Claus Ibsen"  wrote:
>>
>> On Wed, Dec 4, 2013 at 8:22 AM, Andrew Thorburn  wrote:
>> > Apologies for the spam, but this should be the last post, and I
>> > believe there's a bug somewhere. According the documentation
>> > (http://camel.apache.org/simple.html), I should be able to do
>> > something like this:
>> >
>> > ${in.header.type} is 'java.lang.String'
>> >
>> > And I will get back true or false. However, the following
>> >
>> > 
>> > > > resultType="java.lang.Object">${in.headers[soap.header.globalRequestHeader]}
>> > is 'com.test.GlobalRequestHeader'
>> > 
>> >
>>
>> This is an expression and not a predicate.
>>
>> You would need to set the resultType to boolean so Camel would know
>> its a predicate.
>> And not sure if Camel 2.10.x is too old to support that way.
>> Newer releases sure does.
>>
>>
>>
>>
>>
>>
>> > Sets the header to the following value:
>> >
>> > 
>> > > > xmlns:ns2="uri:com:test">
>> > ?
>> > ?
>> > 
>> >  is 'com.proaxiom.hsbc.xsd.request.GlobalRequestHeader'
>> >
>> > OK, possibly that's due to setting it to java.lang.Object.
>> >
>> > I tried again, but with resultType="java.lang.Boolean" and got back
>> > "false", which is pretty clearly not correct. Tried a few variations
>> > on that, and the value on the left is always converted to a String
>> > before any further processing is conducted, making the "is" operator a
>> > bit pointless (in one case, using ${bean:camelContext}, I got a nasty
>> > exception, which I can share if needed). I assume this is a bug? Has
>> > it been fixed in a later version of Camel?
>> >
>> > - Andrew
>> >
>> > On Wed, Dec 4, 2013 at 8:03 PM, Andrew Thorburn 
>> > wrote:
>> >> I should add here that I want to log the result, so I have something
>> >> like:
>> >>
>> >> > >> loggingLevel="INFO" />
>> >>
>> >> But even with the following:
>> >>
>> >> 
>> >> > >> resultType="java.lang.Object">${headerAs(soap.header.globalRequestHeader,
>> >> com.test.GlobalRequestHeader).getRegion()}
>> >> 
>> >>
>> >> I still get the raw XML instead of the value of the region property.
>> >> It basically seems that what I want isn't possible, and that even
>> >> thinking about using SOAP headers here was a terrible idea, given the
>> >> amount of pain it's caused me.
>> >>
>> >> Thanks,
>> >>
>> >> - Andrew
>> >>
>> >> On Wed, Dec 4, 2013 at 7:50 PM, Andrew Thorburn 
>> >> wrote:
>> >>> I've been having a bunch of trouble trying to do something that seems
>> >>> like it should be really simple... Using Camel 2.10.7 on ServiceMix
>> >>> 4.5.2.
>> >>>
>> >>> Basically, I'm sending a SOAP message, which contains a SOAP header
>> >>> that looks like this:
>> >>>
>> >>>   
>> >>>  ?
>> >>>  ?
>> >>>  ?
>> >>>   
>> >>>
>> >>> Camel takes the bean from a CXF Endpoint in Payload format, and then
>> >>> adds the SOAP headers to the Exchange Headers. In this case, the SOAP
>> >>> header is being marshalled via JAXB before being added to the Exchange
>> >>> Headers (so it's put into the headers as an object).
>> >>>
>> >>> I now have a com.test.GlobalRequestHeader object in my exchange
>> >>> headers, and want to access the property region, say.
>> >>>
>> >>> How do I do this?
>> >>>
>> >>> I've tried ${headerAs(soap.header.globalRequestHeader,
>> >>> com.test.GlobalRequestHeader).region} and that doesn't work. I've
>> >>> tried a bunch of other ways of doing in via Simple, and it just does
>> >>> not work. Checking TRACE logs, I see that it's always being converted
>> >>> to a String, instead of having methods called on it, which is a bit
>> >>> strange. Is it possible that the fact that it's a JAXB-annotated class
>> >>> is interfering with the Simple language somehow?
>> >>>
>> >>> I can definitely access the header, because

Re: Passing parameter to Bean

[Christian Posta]

inject it into your route builder as a String, then you can use it in
your route or reference it somehow

On Wed, Dec 4, 2013 at 2:49 PM, zahir  wrote:
> Hello,
>
> I have a property file defined in applicationContext.xml
>
>http://camel.apache.org/schema/spring";>
>  
> transformation
>   
>
> there is property there in above property file names xx. I want to get its
> value in bean class, but I am not able to pass it. Here is my bean class
> only method:
>
> public  String  map(String args) { ... }
>
>
> I can get the property in route using {{xx}}, but not sure how to pass it to
> bean.
>
> Any advice will be appreciated.
>
>
> Thank you
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Passing-parameter-to-Bean-tp5744331.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta

Re: DSL Logging not outputting to the logs

[mckinnonrob]

Claus Ibsen-2 wrote
> The log uses the route name as the logger name by default.
> 
> You can try to specify a logger name to use with the 3 args version
> public Type log(LoggingLevel loggingLevel, String logName, String
> message) {

I specified the three args version with the following:
from("jms:queue:CAMEL_IN").to("multiplier").*log(LoggingLevel.ERROR,
"com.test.Foo", "this is a test ${body}")*.to("jms:queue:CAMEL_OUT");

Still not seeing the log statement from the route however the following logs
are being produced:

2013-12-04 20:40:36 DEBUG
org.apache.camel.component.jms.DefaultJmsMessageListenerContainer:313 -
Received message of type [class
org.apache.activemq.command.ActiveMQTextMessage] from consumer
[PooledMessageConsumer { ActiveMQMessageConsumer {
value=ID:robs-MacBook-Pro.local-61189-1386207612100-1:2:2:1, started=true }
}] of session [PooledSession { ActiveMQSession
{id=ID:robs-MacBook-Pro.local-61189-1386207612100-1:2:2,started=true} }]
2013-12-04 20:40:36 DEBUG
org.apache.camel.component.jms.JmsConfiguration$CamelJmsTemplate:464 -
Executing callback on JMS Session: PooledSession { ActiveMQSession
{id=ID:robs-MacBook-Pro.local-61189-1386207612100-1:2:2,started=true} }


Claus Ibsen-2 wrote
> And do you run your Camel app is some container or does this happen
> also from an unit test or running standalone etc?

I have been using the maven plugin "mvn camel:run"




--
View this message in context: 
http://camel.465427.n5.nabble.com/DSL-Logging-not-outputting-to-the-logs-tp5744093p5744340.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: DSL Logging not outputting to the logs

[mckinnonrob]

Raul Kripalani wrote
> Are you getting any other log statements printed out to your 'out' console
> appender?

Yes. I am seeing all the log chatter. Just not seeing logs from the route.



--
View this message in context: 
http://camel.465427.n5.nabble.com/DSL-Logging-not-outputting-to-the-logs-tp5744093p5744341.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Passing parameter to Bean

[zahir]

Thank you for your reply. Could you show me an example.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Passing-parameter-to-Bean-tp5744331p5744343.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Accessing property on bean in header?

[Andrew Thorburn]

Had another crack at this, and my ultimate problem was that I didn't
read the documentation carefully enough - I can do what I want, just
not how I wanted to do it.

What I wanted to have was a property called "a.b.c", and then be able
to call an OGNL expression on it. I had thought I could do it by using
the following fashion to get a header: in.headers[a.b.c].OGNL - that
does not work, and the documentation does not list that as a
possibility - OK, that's my bad, and I'll raise a feature request if I
want to see supported.

The other way I had initially tried, which had not worked, was
in.headers.a.b.c.OGNL - if I want to use an OGNL expression to access
a header property, I cannot have a '.' in the name of the header.
That's something I feel the documentation could be clearer on, though
it never said my way would work, and after a bit of though I'm not
surprised that it doesn't work.

Anyway, I can do what I want, I just have to name my header
soap_header_* instead of soap.header.* (or what have you - just so
long as the header name does not contain a period). Case closed.

Thanks,

- Andrew

On Thu, Dec 5, 2013 at 2:15 PM, Andrew Thorburn  wrote:
> Something is broken here - not sure if it's me or Camel, but I can't
> say that I expected that,given the following:
>
> setHeader("test").simple("${in.header.simpleBean} == null",
> Boolean.class).setHeader("test2").simple("${in.headers.simpleBean} !=
> null", Boolean.class)
>
> *Both* headers are false! This is using Camel 2.12.2, so the latest
> version. The full output and code is here:
> http://pastebin.com/xdSsatEP, and it's pretty simple, so if someone
> could explain what I'm doing wrong that would be awesome.
>
> The header, simpleBean, is definitely not null - that's confirmed in a
> log message and by actually checking the header in another processor,
> so I think something has gone horribly wrong in Camel... I also still
> can't extract properties from header objects, so I'm assuming that's
> not supported.
>
> Thanks,
>
> - Andrew
>
> On Wed, Dec 4, 2013 at 8:36 PM, Andrew Thorburn  wrote:
>> Yes, I did eventually figure that out, and when I did, the predicate returns
>> false due to the left-hand side being converted to a String before the
>> comparison takes place. Given that it's probably a bug, is it likely fixed
>> in a later version of Camel? I'll try to check it myself, probably in a day
>> or so.
>>
>> - Andrew
>>
>> On 4/12/2013 8:28 PM, "Claus Ibsen"  wrote:
>>>
>>> On Wed, Dec 4, 2013 at 8:22 AM, Andrew Thorburn  wrote:
>>> > Apologies for the spam, but this should be the last post, and I
>>> > believe there's a bug somewhere. According the documentation
>>> > (http://camel.apache.org/simple.html), I should be able to do
>>> > something like this:
>>> >
>>> > ${in.header.type} is 'java.lang.String'
>>> >
>>> > And I will get back true or false. However, the following
>>> >
>>> > 
>>> > >> > resultType="java.lang.Object">${in.headers[soap.header.globalRequestHeader]}
>>> > is 'com.test.GlobalRequestHeader'
>>> > 
>>> >
>>>
>>> This is an expression and not a predicate.
>>>
>>> You would need to set the resultType to boolean so Camel would know
>>> its a predicate.
>>> And not sure if Camel 2.10.x is too old to support that way.
>>> Newer releases sure does.
>>>
>>>
>>>
>>>
>>>
>>>
>>> > Sets the header to the following value:
>>> >
>>> > 
>>> > >> > xmlns:ns2="uri:com:test">
>>> > ?
>>> > ?
>>> > 
>>> >  is 'com.proaxiom.hsbc.xsd.request.GlobalRequestHeader'
>>> >
>>> > OK, possibly that's due to setting it to java.lang.Object.
>>> >
>>> > I tried again, but with resultType="java.lang.Boolean" and got back
>>> > "false", which is pretty clearly not correct. Tried a few variations
>>> > on that, and the value on the left is always converted to a String
>>> > before any further processing is conducted, making the "is" operator a
>>> > bit pointless (in one case, using ${bean:camelContext}, I got a nasty
>>> > exception, which I can share if needed). I assume this is a bug? Has
>>> > it been fixed in a later version of Camel?
>>> >
>>> > - Andrew
>>> >
>>> > On Wed, Dec 4, 2013 at 8:03 PM, Andrew Thorburn 
>>> > wrote:
>>> >> I should add here that I want to log the result, so I have something
>>> >> like:
>>> >>
>>> >> >> >> loggingLevel="INFO" />
>>> >>
>>> >> But even with the following:
>>> >>
>>> >> 
>>> >> >> >> resultType="java.lang.Object">${headerAs(soap.header.globalRequestHeader,
>>> >> com.test.GlobalRequestHeader).getRegion()}
>>> >> 
>>> >>
>>> >> I still get the raw XML instead of the value of the region property.
>>> >> It basically seems that what I want isn't possible, and that even
>>> >> thinking about using SOAP headers here was a terrible idea, given the
>>> >> amount of pain it's caused me.
>>> >>
>>> >> Thanks,
>>> >>
>>> >> - Andrew
>>> >>
>>> >> On Wed, Dec 4, 2013 at 7:50 PM, Andrew Thorburn 
>>> >> wrote:
>>> >>> I've been having a bunch of trouble trying to do something that seems
>>> >>> like it shoul

Passing multiple parameters to CXF endpoint

[trilochan237]

Hi,
Can anyone help in passing multiple parameters to the CXF endpoint which is
expecting multiple parameters.

 from("direct:test1").process(new Processor() {

@Override
public void process(Exchange arg0) 
throws Exception {

arg0.getOut().setBody("testmessage");

}

}).to("cxf://http://localhost:8085/FinEdge-General/xrmServices/2011/Organization.svc?serviceClass=com.hcl.flsl.integration.msdn.crmwcf.IOrganizationService";);

Error I am facing is:

et the wrong parameter size to invoke the out service, Expect size 3,
Parameter size 1. Please check if the message body matches the CXFEndpoint
POJO Dataformat request.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Passing-multiple-parameters-to-CXF-endpoint-tp5744345.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: problems with route cxf -> netty

[troesler]

what i have found out

   this configures it as server
socket where clients can connect

  this configures it as
client that can connect to a server socket

now if i have this route




is there any way to configure netty/mina etc as a server socket and not a
client with the  tag?
or might anyone have an idea for a workaround for this?

someone else already had a similar problem according to this
https://issues.apache.org/jira/browse/CAMEL-1077 "tcp client mode / server
mode determined by "to" or "from" elements limits usability."



--
View this message in context: 
http://camel.465427.n5.nabble.com/problems-with-route-cxf-netty-netty-as-tcp-socket-server-tp5744294p5744346.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Spring AMQP Apache Camel Component Released

[muthukumara...@gmail.com]

Hi,

I tried to use your component and it works perfectly fine. I did test it
with our minimal testcases and things worked fine.

Is this component ready to be used for production use?

Thanks,
Muthu



--
View this message in context: 
http://camel.465427.n5.nabble.com/Spring-AMQP-Apache-Camel-Component-Released-tp5027785p5744342.html
Sent from the Camel - Users mailing list archive at Nabble.com.