It looks you are setting the message header rightly.
Can you send me a test case ? So I can debug the issue with it.
BTW, which version of Camel are you using ?
On 3/15/11 2:42 AM, tjain2011 wrote:
Hi
Can you please elaborate on this. I am in the similar situation. How did you
set the
operation
You can use the Camel transport[1][2] of CXF to delegate the transport to
camel-jetty like this.
But it needs addition spring configuration configuration on the cxf
endpoint.
[1]http://camel.apache.org/camel-transport-for-cxf.html
[2]http://camel.apache.org/cxf-example.html#CXFExample-CXFexamplef
Hi,
We have recently upgraded to Camel 2.5.0 from 1.4.0.
Almost everything seems to be working after making all the necessary
changes.
I'm attaching a route definition as a separate file.
In my route i am posting an xml message to a recipientList which maybe
http/ftp/sftp.
Now, everything seems to
You might be having issues with ActivMQ flow control.
I blogged about similar problem a while back. http://www.dragishak.com/?p=254
Basically, there is a limit on the total number of messages buffered in AMQ. In
a transacted route a message will not be taken off the queue unless the
transaction
Thanks for your response. As mentioned I cleaned up the routes to be as
basic as possible to replicate the issue we are facing. Let me describe
why we have this type of routing and what we are trying to accomplish...
1. Start transaction 1
2. Consume message from queue foo
3. Perform so
Hi,
It is quite unclear why/what you are really trying to do.
First, When you say PROPAGATION_REQUIRED, you pass the transaction context
along the route hoping that somewhere along the way following proper
processing, the exchange will come back in a state where a commit/rollback
can be done on t
Hi,
All endpoint(producers and consumers) are known to the camel context and the
camel context is responsible for cleanup during shutdown.
The components that create the endpoints (HTTP, JMS etc) are responsible for
implementing methods such as doStop() which is invoked by the CamelContext
in ord
Hi,
What you need to do is something like what is given below.
Sorry, I am no expert on OpenMQ so you will need to figure this bit out on
your own...
Cheers,
Ashwin...
=
Put this in the Spring XML file
Hi,
What you need to do is something like what is given below.
Sorry, I am no expert on OpenMQ so you will need to figure this bit out on
your own...
Cheers,
Ashwin...
=
Put this in the Spring XML file
===
Hi,
The details in your email are rather sketchy. However based on the error, it
seems like your payload sent to the webservice does not match up in terms of
input/output parameters on the producer and consumer endpoints.
In addition, in order to receive a response the web service method invoked
Am 15.03.2011 15:04, schrieb Claus Ibsen:
We could maybe detect the return type is a Future, and offer support
for that. I don't know how easy that would be.
That said its my impression that its only a few Camel end users who
needs to use the Future API.
Hmm, if you don't use Futures, is ther
The following sample:
http://camel.465427.n5.nabble.com/file/n3710309/FirstTest.java
FirstTest.java
shows the same issue with only 2 messages sent to 2 distinct endpoints.
if instead of using a single interceptor "(ftp|sftp|ftps|http):.*"
2 distinct interceptors are defined:
"(ftp|sftp|ftps):.*
to make it run in exception you don't even need to run a cycle of with many
messages sent, you just need to define an the interceptor for ftp and http:
interceptSendToEndpoint("(ftp|sftp|ftps|http):.*").process(
new Processor() {
public void process(Exchange exchange) throws Exception {
One component per CamelContext.
Hadrian
On Mar 15, 2011, at 12:08 PM, tnk wrote:
> Hi,
>
> i am new to camel (i use it in serviceMix), so the question might sound
> strange. How many instances of component class are created?
> For example, i use camel-cache component in several different bun
why isn't the route running in exception if instead of using an intercept
send to endpoint for all protocols I define 2 different inteceptors, 1 for
ftp and 1 for http?
--
View this message in context:
http://camel.465427.n5.nabble.com/java-util-concurrent-RejectedExecutionException-using-interce
Hi,
i am new to camel (i use it in serviceMix), so the question might sound
strange. How many instances of component class are created?
For example, i use camel-cache component in several different bundles,
injected with
@EndpointInject(uri = "cache://cacheName?properties") //uri is differe
Is there a way to access the list of camel producers and cleanup all
instances so that they can be collected by the garbage collector?
--
View this message in context:
http://camel.465427.n5.nabble.com/cleanup-camel-cached-producers-tp3708189p3708189.html
Sent from the Camel - Users mailing list
Hi,
What you are running into is an issue related to the JMS Spring Template
where setting the cache level to none actually gets rid of the connection
and session object per invocation thereby losing any knowledge of its
precious connection (aka Memento). While a pool may indeed exist the
connecti
There is a CXFNonSpringServlet that you use to configure what you
would like to do
http://cxf.apache.org/docs/servlet-transport.html
On Tue, Mar 15, 2011 at 2:59 PM, davsclaus wrote:
> Interesting case.
>
> I wonder if Apache CXF offers a pluggable API so the camel-cxf component
> could be able
Hi
On Mon, Mar 14, 2011 at 9:33 PM, Harald Wellmann wrote:
> Is it possible to combine remoting by proxy
> (http://camel.apache.org/spring-remoting.html) with asynchronous
> request/reply (http://camel.apache.org/async.html) to achieve some sort of
> equivalent to EJB 3.1 @Asynchronous invocation
Interesting case.
I wonder if Apache CXF offers a pluggable API so the camel-cxf component
could be able to leverage existing Jetty instance from the camel-jetty
component.
Willem do you have a comment on this?
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-embedded-
See this FAQ
http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
--
View this message in context:
http://camel.465427.n5.nabble.com/my-webservice-has-a-return-type-as-a-java-object-the-exchange-out-is-null-tp3674745p3704546.html
Sent from the Camel - Users mailing list archive
On Tue, Mar 15, 2011 at 3:19 AM, hyjshanghai wrote:
> Thanks.
>
> I have set handleFault to "true" on my camel context. But the processor
> configured in onException(java.lang.Exception) still fails to execute if the
> cxf endpoint returns soap fault message.
>
> The cxf endpoint that returns soap
I think you should set the Header and DefaultOperationName of
exchange.getOut(), not those of exchange.getIn().
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-CXF-Producer-should-allow-setting-of-BindingOperationInfo-tp3258474p3696949.html
Sent from the Camel - Users mai
Ooops, it was to be my entire fault :-/
I my test case, I had the following MockEndpoint declaration:
from("seda:incoming.stocks").to(mockStocks);
With that extra endpoint consumer, the result of
endpoint.getConsumers().size() in the SedaEndpoint.sendToConsumers(..)
method was 2 and not 1, henc
Hello,
I'm trying to use an unmarshaller within a route that starts from a seda
endpoint:
from("seda:incoming.stocks")
.unmarshal(stockUnmarshaller)
.to("jpa:stock.domain.IntegrationStock?usePersist=true");
Basically, this endpoint consumes XML messages i
Hello list!
I have a question related to the
org.apache.camel.processor.aggregate.AggregationStrategy in conjunction with
the enrich DSL, the onException definition and a thrown exception (we are
using Camel 2.2.0-fuse-02-00).
Our simplified route looks like the following:
{code}
onException(Exce
I found the problem. I need to add my context to the servletcontext...
--
View this message in context:
http://camel.465427.n5.nabble.com/CXFServlet-not-correctly-initialized-by-ResourceXmlApplicationContext-tp3556429p3691776.html
Sent from the Camel - Users mailing list archive at Nabble.com.
After a bit of investigating I managed to resolve this problem. Apparently,
Serv-U uses UTF-8 for "control encoding". I believe this is the most common
encoding and, to my understanding, if the ftp server supports UTF-8 then it
should be used unless the ftp client requests otherwise.
If I add the
29 matches
Mail list logo
