Hi,
Please allow me to subscribe.
Thanks,
Arthanarisamy
--
*Disclaimer*
This e-mail and the attachments thereto contain confidential information
and are intended only for the individual to whom it is addressed. If you
are not the intended addressee, then you are hereby notified that
.
spring-ws://https://something.com:4443/Webservices/service.swe?Cmd=Execute&Source=WebService&WSSOAP=1
How do i pass query parameters using Camel Spring-ws?
Thanks,
Arthanarisamy
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Spring-WS-Endpoint-with-URL-Query-Pa
Your end point URL should be appended with messageFactory
eg:
.doTry()
.to("cxf://" + CxfUrl + "?" + "wsdlURL=" + WsdlUrl+ "&" + "serviceName=" +
ServiceName + "&" + "portName=" + interpolPortName + "&" +
"headerFilterStrategy" + "=#" + "propagateAllHeaderMessages" + "&" +
"dataFormat=" + interp
Hi,
You should also set messageFactory accordingly.
--
View this message in context:
http://camel.465427.n5.nabble.com/Calling-Soap-1-1-Service-from-Camel-cxf-via-Java-DSL-tp5757538p5757539.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yes Camel-EJB itself. :)
--
View this message in context:
http://camel.465427.n5.nabble.com/Integrate-Remote-EJB-s-using-Camel-tp5757372p5757379.html
Sent from the Camel - Users mailing list archive at Nabble.com.
We have used Spring XML based configurations and endpoints, jndi details are
all configured in XML.
When you use JAVA DSL, hope the same can be addressed using properties file
as well.
--
View this message in context:
http://camel.465427.n5.nabble.com/Integrate-Remote-EJB-s-using-Camel-tp57573
As far as i know there no specific example or documentation about invoking
EJB through Camel.
But in our application we invoke remote EJB's using Apache Camel only and
integration is easy with it.
--
View this message in context:
http://camel.465427.n5.nabble.com/Integrate-Remote-EJB-s-using-Ca
Hi Willem Jiang,
First of all thanks a lot for your reply and which gave me some insight on
ProducerTemplate threads in waiting state.
I have one more issue.
I am invoking an EJB which is deployed in Jboss jboss-as-7.1.1.Final. Below
is piece of code i am using to invoke and EJB.
private void
I am able to receive the response when the EJB is deployed in any other
Application Servers(IBM Websphere and Weblogic).
Please let me know what is causing issue in Jboss.
Thanks,
Arthanarisamy
--
View this message in context:
http://camel.465427.n5.nabble.com/No-EJB-receiver-available-for-h
Thanks Claus for the timely support.
--
View this message in context:
http://camel.465427.n5.nabble.com/Custom-Thread-Pool-Profile-maxPoolSize-tp5753199p5753204.html
Sent from the Camel - Users mailing list archive at Nabble.com.
with 50 concurrent users with concurrent
sessions, which means there will be 50 concurrent requests but could see
only 20 threads at any given time.
Thanks,
Arthanarisamy
--
View this message in context:
http://camel.465427.n5.nabble.com/Custom-Thread-Pool-Profile-maxPoolSize-tp5753199.html
Sent
Hi Matt,
Thanks for the reply, actually i do not get any exceptions as the external
service returns a success response.
Below is code used to invoke a EJB service
Future futurexchange = (Future)
p_ProducerTemplate
.asyncSend(FrameworksStartup.get
is the time difference between Completed and Sent.
Or if there will be time difference between above said events, please do let
me know why is the delay.
Thanks,
Arthanarisamy
--
View this message in context:
http://camel.465427.n5.nabble.com/ExchangeSentEvent-spent-time-is-more-than-ExchangeComp
To handle timeout on client side for EJB service call, i used
Future and had set time out time over future object. Having this,
both success and time out cases are working fine.
But the problem here is when i take thread dump i could see that the thread
is in waiting state.
When i manually stop an
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:19
15 matches
Mail list logo