the client request header will still effect on the second
camel-cxf endpoint.
--
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
Hi,
I just add an unit test to show how to set the HttpClientPolicy dynamically.
You can set the receive timeout through the message header like this[1]
http://svn.apache.org/viewvc?rev=1402926view=rev
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
is passed to your SearchController. Then you can
create a template as you want.
--
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
You can add Processor[1] or bean method[2] to do the job here.
[1]http://camel.apache.org/processor.html
[2]http://camel.apache.org/bean.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
-caching.html
--
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.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
Hi,
It looks more like Activemq issue instead of camel-jms issue.
Did you try to ask the question in the activemq user mailing list?
--
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
Hi,
Which version of camel are you using?
I just did some test against the camel trunk ( camel-2.11-SNAPSHOT). I cannot
reproduce the error.
BTW, you should be able to get the message header CamelHttpQuery with value
of wsdl. Hope you can find workaround with this message header.
--
Willem
It could be helpful if you can show us your camel route definition.
--
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
Hi,
Did you try the address https://localhost:443/cxf/example?
--
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
I don't think Camel xpath[1] can provide the function that you want.
You can use a bean method [2] with @Xpath annotation to do that kind of job.
[1]http://camel.apache.org/xpath.html
[2]http://camel.apache.org/bean-language.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Can you past the whole stack trace?
It hard to tell the error from your discription.
--
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
You can let camel invoke the WebService by using the WebService client you
generated in the bean[1] or Processor[2].
Then you don't need to use SOAP data bind or camel-cxf any more.
[1]http://camel.apache.org/bean.html
[2]http://camel.apache.org/processor.html
--
Willem Jiang
Red Hat, Inc
Hi,
I think you need to checkout the log file to see if there is any related error.
BTW, as camel 2.10 does not use the Spring 3.1.x out box, you may need to check
the class patch setting of you test.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
We only have some unit tests on AMPQ :(
--
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.javaeye.com (http
Hi,
You can define the method of your bean like this
import org.apache.camel.language.XPath;
public void changeStatus(String value, @XPath(//Root/Key/text()) String key) {
…...
}
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
camel-zookeeper component[1] can help you to do that.
[1]http://camel.apache.org/zookeeper.html#Zookeeper-ZooKeeperenabledRoutepolicy.
--
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
Hi
I'm not sure why the AMQ connection is closed from the RabbitMq side.
From the Camel side log everything look good.
--
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
Yeah, camel-jms component need the message body to be Serializable.
Or you need to marshal and unmarshal the POJO with JAXB or other date format.
BTW, I just committed the test into the trunk[1]
[1]http://svn.apache.org/viewvc?rev=1399986view=rev
--
Willem Jiang
Red Hat, Inc.
FuseSource
Hi,
If you just want to send a String back the client when the exception is thrown,
you can just create a method as toResultString in the ProcessError Object.
And it could be used with the ErrorHandler.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
Hi Robert
I can reproduce the error that you meet. I'm looking it now.
--
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
/
camel:to uri=context:fooCamelContext:foo.in (http://foo.in)/
/camel:route
/camel:camelContext
camel:camelContext id=fooCamelContext streamCache=true
camel:route
camel:from uri=direct:foo.in (http://foo.in)/
camel:to uri=log:local.com.foo/
/camel:route
/camel:camelContext
--
Willem Jiang
Red Hat
Hi,
I filled a JIRA [1] and committed an enhancement for it.
It could give us more meaningful information if we don't setup the camel
context rightly.
[1]https://issues.apache.org/jira/browse/CAMEL-5714
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
Please see my comments in the line.
--
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.javaeye.com (http://jnn.javaeye.com
You can set the message header CamelFileName dynamically in a processor.
This processor can get the FileName from the message body.
--
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
--
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.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo
I think I can add one to the camel trunk.
I will let you know when I commit the code.
--
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
--
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.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo
Hi,
It looks like you are using camel spring Main to load the camel application
context.
I'm not sure why your mvn project have the dependency of
camel-archetype-spring:jar:1.0-SNAPSHOT.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
Hi,
I think you can use the ErrorHandler to catch the Exception in a genetical way.
What's your ProcessError class looks like?
--
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
As I know the Trace just log the exception, it will not catch the exception.
Camel Error handler can do that kind of work.
Please forget about the InOnly data format, I should say the InOnly Message
Exchange Pattern.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
I think the most convenient is define a ShutdownStrategy and configure it into
you camel context with the Spring DSL.
--
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
be great
if you are plan to submit a patch for it :).
[1]https://issues.apache.org/jira/browse/CAMEL
[2]http://camel.apache.org/contributing.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
It is hard to tell why the NPE was thrown.
Can you try to deploy the application into other WebContainer to see if it
works ?
--
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
Hi,
I just checked the camel-cxf trunk, it doesn't create the JaxWsClientProxy any
more.
Can you try to upgrade the camel version to pick latest CXF version for it ?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog
-example.html
--
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.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
Hi
I'm afraid camel-ahc component doesn't provides the Webdav implementation for
you.
It could be easy if you use the Sardine API to build up component for do kind
of work.
Anyway, it could be great if you can contribute the implemented component to
camel :)
--
Willem Jiang
Red Hat
It looks like you are using InOnly data format.
Can you check if there is any exception is thrown in the camel log?
--
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
,
org.apache.cxf.message.Message.class);
Then you can tried to access the Headers like this
ListHeader soapHeaders = (ListHeader)
cxfMessage.getHeader(Header.HEADER_LIST)
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
.
--
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.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo
I just you specify the bindingId=service:EchoServiceSOAP11Binding for the
echoService.
Maybe you should double check it :)
--
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
[2]https://svn.apache.org/repos/asf/camel/trunk/components/camel-cxf/src/test/java/org/apache/camel/component/cxf/CxfProducerContextTest.java
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
the
response back in the CXF service implementation class without use camel-cxf
component.
--
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
to help you :)
--
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.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter
(new Processor() {
public void process(final Exchange exchange) {
Message in = exchange.getIn();
// get the cxfMessage from camel message header
org.apache.cxf.message.Message cxfMessage =
in.getHeader(CxfConstants.CAMEL_CXF_MESSAGE,
org.apache.cxf.message.Message.class);
…...
}
--
Willem
How did you call the convert method?
I need have a look at bean method of jmsCacheServer.
--
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
Hi
I don't get what the instance that you mention in your questions.
Camel will create a new Message when it get the mms from the topic queue.
I don't know how you link the processRequest route to sendPesponse route.
It is important for us to answer the question of 4.
--
Willem Jiang
Red
the FailOverLoadBalancer directly without any addition
work.
--
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.javaeye.com (http
Hi,
The exception is thrown as the cxf endpoint need to access the WSDL to build
the service module.
You can work around it by store the WSDL in your local directory.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog
context listener which loads the XML file --
listener
listener-classorg.springframework.web.context.ContextLoaderListener/listener-class
/listener
….
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
You can also start a camel context by using the Camel web console[1].
[1]http://camel.apache.org/web-console.html
--
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
No, you don't need to export 10 cxfEndpoint to invoke the 10 different methods.
There are some message headers can help CxfProducer to decide which method it
will use.
operationName, operationNamespace
You just need to set them up once you decide to invoke the external WebService.
--
Willem
Can you try to set the operation in the URI like this?
cxf:bean:helloWorld?wrappedStyle=true
--
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
The Splitter will remove the line, as you just use the regex token like
C.*?PAG\. 1.*?.
Camel will create a list for splitter to use.
--
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
of
CollectionTransform like this
class CollectionTransformerFactoryBean implements
FactoryBeanTransformerString, Long {
public TransformerString, Long getObject() throws Exception {
return new CollectionTransformerString, Long;
}
…...
}
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part
Hi
Can you change the transportID in you WSDL from
http://schemas.xmlsoap.org/soap/http; to
http://schemas.xmlsoap.org/wsdl/soap/http;
to workaround this issue?
It looks current CXF SoapBindingFactory doesn't make a right mapping for it.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now
I just checked the CXF code, there is an entry of
http://schemas.xmlsoap.org/soap/http;
You should use http://schemas.xmlsoap.org/soap/http; instead of
http://schemas.xmlsoap.org/soap/http/;
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
We need to clean up the namespace of SoapTransportFactory, as the
http://schemas.xmlsoap.org/soap/http/; is not a validate namespace.
I just filled a JIRA[1] for it.
[1]https://issues.apache.org/jira/browse/CXF-4554
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
It looks like a JPA (EclipseLink) related error.
What kind of camel components are you using?
--
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
Camel has the GenericFileFilter[1] interface that you can use the do this kind
of job.
[1]http://camel.apache.org/ftp2.html#FTP2-Filterusing%7B%7Borg.apache.camel.component.file.GenericFileFilter%7D%7D
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
It's depends on what's version of service mix are you using.
As Apache Camel provides patch releases, it could be possible that you just
replace the camel-netty or camel-mina jars with that latest one.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
It looks like the message body is null, can you double check it ?
--
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
/SwaptionCompactService.wsdl]
--
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.javaeye.com (http://jnn.javaeye.com/) (Chinese
Can you try to use the more latest Camel version?
I think it could be better if you are trying to use CXF 2.5.x.
BTW, how did deploy your camel route?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
Hi,
Current camel-velocity doesn't support to check the property configuration file
periodically,
It only load it when the camel-velocity endpoint is started, and will not
reload it per request.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com
Basically, you just need to find out the RouteBuilder classes as you want in
Java when you extends the CamelConfiguration class, then you don't need to be
bothered by any XML.
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
You can enable the trace[1] feature to see if the message is sent to jms
endpoint.
[1]http://camel.apache.org/tracer.html
--
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
How did you stop the consumer, I'm not sure if the consumer still hold the
first message when you stop the consumer.
What kind of JMS ACKNOWLEDGE did you use?
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
Just quick note, if you are using CXF 2.5.x, you don't need to specify the
below line in your spring configuration file
import resource=classpath:META-INF/cxf/cxf-servlet.xml/
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http
You may also need to take a look at the camel-servlet component[1].
It's not an easy job to combine the Servlet, CamelContext within the OSGi
platform.
[1]https://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
the Java
object of PriceReuqestMessage from the message body.
[1]http://camel.apache.org/cxfrs.html
--
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
Hi,
You need to take a good look at the camel-servlet[1] component, as you want to
get the file name from the client http request.
[1]http://camel.apache.org/servlet.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
camel-servlet is using the CamelServlet as the servlet name by default.
You can use the servletName option to specify the servlet name as you want.
Like this
from(servlet:/hello?servletName=CamelServlet1).transform(simple(Hello
${header.name}));
--
Willem Jiang
Red Hat, Inc.
FuseSource
You can use the ProducerTemplate sendBodyAndHeaders method.
It will take a map as the headers those you want to send the endpoint.
--
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
It could easy to implement your requirement by add a customer MockComponent
which just look up the created MockEndpoint if the uri is end with *.
But I'm not sure why do you want to create the same mock endpoint with the uri
with different the query parameters.
--
Willem Jiang
Red Hat, Inc
I just committed the patch[1] of it into the trunk.
Please check out the camel-2.11-SNAPSHOT to verify the patch.
[1]http://svn.apache.org/viewvc?rev=1387889view=rev
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog
I think the user wants to set the response message by leveraging the
mock endpoint.
It could be easier by using sending intercepter.
2012/9/21, Henryk Konsek hekon...@gmail.com:
Hi guys,
from(direct:start).process(new
ClassThatGeneratesDynamicUriHeader()).recipientList(header(DynamicURI));
Hi,
You can take a look at the camel-quratz[1] and camel-ftp[2] component.
[1]http://camel.apache.org/quartz.html
[2]http://camel.apache.org/ftp2.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com | http://www.redhat.com
Blog: http
You can set if the route is started[1] when the camel context is started.
Then you can start the route as you want in when the other route is ready.
[1]http://camel.apache.org/configuring-route-startup-ordering-and-autostartup.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red
I think we can add a printer prefix option on the camel-printer endpoint to
help us find the right printer we want.
I just fill a JIRA[1] for it.
[1]https://issues.apache.org/jira/browse/CAMEL-5630
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com
The ZooKeep endpoint configuration should not be effected by the other
endpoints.
I just filled a JIRA[1] and will commit the fix as you suggested shortly.
[1]https://issues.apache.org/jira/browse/CAMEL-5627
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http
It makes sense to add an option which can help user to load the routes they
need.
If you are using Spring, you can setup a camel context which has reference all
the route you need.
I just filled a JIRA[1] for it.
[1]https://issues.apache.org/jira/browse/CAMEL-5617
--
Willem Jiang
I just have a quick look at the article,
it is a good tutorial for the user who want to know about how to use camel.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
It looks more like the issue of user permission.
btw, you can use the camel:run plugin to start the camel application without
using tomcat.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http
No, I dont think the upgrading can resolve the issue, as there is no
much chang in the camel-http4 component. Can you try to invoke the
sevice by using http client4 directly?
Willem
2012/9/13, Adrian Harris adrian.w.har...@gmail.com:
Hi,
Thanks for the response, the workaround was a success.
Instead of using camel-cxf component, this is most effective way to do the load
balancing.
I think you can do some tracing work to see if the xpath expression return the
right ServiceGroupID first.
Then we can keep digging if the sticky load balancing is doing its job.
--
Willem Jiang
-HowtogetandsetSOAPheadersinPAYLOADmode
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: willemjiang
producer with the back end
server address as you did before for load balancer to pickup .
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com
Can you try to use the latest released camel 2.10.1 ?
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese
You need set the seda endpoint parameter on the first one endpoint, because
Camel will pickup the created queue in the next endpoint.
Please change the first route like this
…
.log('direct ${body}')
.to('seda:insert?blockWhenFull=truesize=5')
--
Willem Jiang
FuseSource
Web: http
It's here[1]
[1]http://svn.apache.org/viewvc?view=revisionrevision=1377955
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http
Which version of camel are you using?
I just try the below test in the camel trunk the test is passed.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http
I just checked the code, we don't support the FATAL level, it's a document
issue.
I just updated the wiki page for it.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English
You can take a look at the loan-broker-example[1].
[1]http://camel.apache.org/loan-broker-example.html
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http
-HowtousetheCamelerrorhandlertodealwithexceptionstriggeredoutsidetheroutingengine
[2]http://camel.apache.org/file2.html#File2-Usingconsumer.bridgeErrorHandler
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http
Yeah, I should work.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo
://camel.apache.org/schema/spring;
errorHandler id=noErrorHandler type=NoErrorHandler/
/camelContext
or Java DSL
public void configure() {
errorHandler(noErrorHandler());
……
}
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http
How did you shutdown the camel context?
It looks like you need to wait for the aggregation to aggregate the XML for you
before shutdown the camel context.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http
Could you submit a patch to Camel JIRA for it ?
2012/9/2, krishy calvinkri...@gmail.com:
I experimented with this some more and believe its a race condition
in the HazelcastIdempotentRepository. Patched it and all is well after
that.
--
View this message in context:
Sorry, I missed that line.
Thanks for commit the fix shortly.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com
be defined when you define the route.
--
Willem Jiang
FuseSource
Web: http://www.fusesource.com (http://www.fusesource.com/)
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.javaeye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
1201 - 1300 of 2970 matches
Mail list logo