Hi,
I just have a look at the patch, and I can't just copy the java file
into the repository, as there are some change on the MailBinding.java
since Camel 2.2.0 release, so please send a diff patch which is based on
the current trunk.
Thanks for your contribution.
Willem
tide08 wrote:
I al
I already had patch with JIRA, and I just added a TestCase.
Thanks!
willem.jiang wrote:
>
> +1 for this change, can you submit a patch with an unit test.
> I will be happy to apply it into the trunk :)
>
> Willem
>
> tide08 wrote:
>> Just wanted to check, if this patch/fix made sense? Anyon
Hi,
Are you plan to send the multi replies in your gtMessageProcessor?
If so , you can use ProducerTemplate[1] to do what you want.
For the message processing time, can you check if the gtMessageProcessor
take a long time to process the message?
[1]http://camel.apache.org/producertemplate.htm
+1 for this change, can you submit a patch with an unit test.
I will be happy to apply it into the trunk :)
Willem
tide08 wrote:
Just wanted to check, if this patch/fix made sense? Anyone?
Thanks!
tide08 wrote:
It looks like the mail component does not support charset handling for
alternat
Which version of Camel are you using?
Here is an example of split the message in POJO.
public List splitMessage(@Header(value = "user") String
header, @Body String body) {
// we can leverage the Parameter Binding Annotations
// http://camel.apache.org/parameter-binding-
Hi,
I think you may ask this question in Spring-DM, or Karaf mailing list.
As the question is out of scope of Camel :)
Willem
Bengt Rodehav wrote:
Hello everyone,
I'm trying to use Spring-DM's support for managed-service-factory. My
artifact (deployed in Karaf 1.4) contains the following XML
Hi,
Can I have a look at your route? Basically, camel converter supports
different character by setting the Exchange property with the key
Exchange.CHARSET_NAME and value "UTF-8". In this way camel will set
right character encoding when it need to change the byte into String.
BTW, which vers
Can you try to run the back end service in other box or in different port?
It looks like some underlay HTTP communication error happened when you
undeployed the first service.
Willem
rdomingo wrote:
I need to implement failover for my webservices, but I can't get it working.
I'm struggeling w
I'm seeing some strange behavior with character encoding and the XSLT
component. I'm trying to send a '𝒟' through (Hex: 𝒟).
xsltproc handles the source xml/xsl transform fine. But the Camel
transformation component munges this character into "??".
There was another poster with a similar prob
Just wanted to check, if this patch/fix made sense? Anyone?
Thanks!
tide08 wrote:
>
> It looks like the mail component does not support charset handling for
> alternative part? I can set Content-Type for main body but MailBinding
> does not extract out charset from Content-Type?
>
> Class: M
Hi Claus,
I just added the hint to the Using Camel Proxy wiki page
(http://cwiki.apache.org/confluence/display/CAMEL/Using+CamelProxy).
Greetings
Christian
Am 15.03.2010 20:56, schrieb Claus Ibsen:
On Mon, Mar 15, 2010 at 8:51 PM, Christian Schneider
wrote:
I just found the answer m
On Mon, Mar 15, 2010 at 8:27 PM, Christian Schneider
wrote:
> Am 15.03.2010 16:39, schrieb Claus Ibsen:
>>
>> On Mon, Mar 15, 2010 at 4:21 PM, Hadrian Zbarcea
>> wrote:
>>
>>>
>>> I have nothing against that, but I was making a slightly different point.
>>>
>>> Coding a framework is different tha
On Mon, Mar 15, 2010 at 8:51 PM, Christian Schneider
wrote:
> I just found the answer myself:
> @EndpointInject(uri = "direct:start")
> CustomerService customerService;
>
> The above already does the trick. Well this proves again that sometimes
> asking a question is the best way to find the answe
I just found the answer myself:
@EndpointInject(uri = "direct:start")
CustomerService customerService;
The above already does the trick. Well this proves again that sometimes
asking a question is the best way to find the answer ;-)
Greetings
Christian
Am 15.03.2010 20:38, schrieb Christian
I currently use the following in a test for the soap component:
I define an attribute:
@EndpointInject(uri = "direct:start")
protected Endpoint startEndpoint;
then in the test I use:
CustomerService proxy = ProxyHelper.createProxy(startEndpoint,
classLoader, CustomerService.class);
Is the
I need to implement failover for my webservices, but I can't get it working.
I'm struggeling with this for some time and it really is getting a problem.
I keep getting error below when it needs to failover:
...
org.apache.cxf.interceptor.Fault: Already connected
at
org.apache.camel.compone
Am 15.03.2010 16:39, schrieb Claus Ibsen:
On Mon, Mar 15, 2010 at 4:21 PM, Hadrian Zbarcea wrote:
I have nothing against that, but I was making a slightly different point.
Coding a framework is different than coding an application. With the latter,
one pretty much knows what to expect. Wi
any news on topic ??
I believe I get same error in failover situation, my configuration (I tested
both my endpoints are working by commenting them out one by one):
http://0.0.0.0:8081/fooServer/echo?wsdlURL=http://localhost:8080/fooServer1-0.0.1a-SNAPSHOT/echo?wsdl&serviceName={http://www.telec
You can define the route directly in the test file by extending
CamelTestSupport from the camel-test component.
As an example you can take the following test:
https://svn.apache.org/repos/asf/camel/trunk/components/camel-soap/src/test/java/org/apache/camel/dataformat/soap/SoapClientTest.java
Gr
Dear list,
I am implementing a POJO splitter that takes one message as its input,
and shall split this message into multiple output messages.
My route looks like this:
...
processor = new ContainerProcessor();
from("direct:start").split().method(processor,
"process").to(resultEndpoint);
...
Pro
Sorry, posted to the wrong forum...
/Bengt
2010/3/15 Bengt Rodehav
> Hello everyone,
>
> I'm trying to use Spring-DM's support for managed-service-factory. My
> artifact (deployed in Karaf 1.4) contains the following XML snippet in
> beans.xml:
>
> factory-pid="se.digia.connect.routes.test.con
Hello everyone,
I'm trying to use Spring-DM's support for managed-service-factory. My
artifact (deployed in Karaf 1.4) contains the following XML snippet in
beans.xml:
se.digia.connect.core.api.IService
I then drop a configuration file called
"se.digia.connect.routes.tes
Hi everybody,
I am trying to implement Request reply EIP using JMS and succeded quite
easily, thanks to Camel power :-D
Now I find myself in a strange situation: I need to implement this pattern
where I have one request message and possibly more than one reply,
correlated to the original request.
On Mon, Mar 15, 2010 at 4:21 PM, Hadrian Zbarcea wrote:
> I have nothing against that, but I was making a slightly different point.
>
> Coding a framework is different than coding an application. With the latter,
> one pretty much knows what to expect. With frameworks things are a bit more
> com
actually, I copied Mina component and modifying only the code to share
receivehandler and connection between producer and consumer. I need to be
able to load balance on failure. procuder loadbalances using loadbalancer
component on exception.Consumer just listens for message.
I just had a questio
I have nothing against that, but I was making a slightly different point.
Coding a framework is different than coding an application. With the latter,
one pretty much knows what to expect. With frameworks things are a bit more
complicated. I can see how a developer in a long running, managed app
On Mon, Mar 15, 2010 at 1:10 PM, Hadrian Zbarcea wrote:
> I would also like to see a more aggressive testing strategy, probably using
> 'once' instead of 'pertest'. The only major offender is indeed jmx which
> does not cleanup properly on shutdown, you are correct. We should definitely
> look
I would also like to see a more aggressive testing strategy, probably using
'once' instead of 'pertest'. The only major offender is indeed jmx which does
not cleanup properly on shutdown, you are correct. We should definitely look
into the jmx cleanup, because we cannot always assume the lifeti
By the way we are pretty happy with this this ref-component. It allows
automated unit and system testing of a route way before integration tests!
Give it a try. I guess you will see the advantages pretty soon.
I do not disagree, I do have strong positive feelings regarding Camel :P
What I thou
By the way we are pretty happy with this this ref-component. It allows
automated unit and system testing of a route way before integration tests! Give
it a try. I guess you will see the advantages pretty soon.
christoph meise
-Ursprüngliche Nachricht-
Von: Tarjei Huse [mailto:tar...@scan
Hi,
You might want to look at the Mina component source code for gathering
details on how to write a mina like component yourself. But I suspect you
have done this already ;)
Cheers,
Ashwin...
anandsk wrote:
>
> since there is a bug with async route with Mina in camel 2.2.0,
> I am thinki
Do not have both uri and ref on @EndpointInject. Only one of them.
Ah,
but then I will have to define those endpoints outside the test - which it
was my goal not to.
Anyhow, thanks for helping me. I'll place the endpoint definitions in a
separate file.
Regards,
Tarjei
Claus Ibsen-2 wrote:
Do not have both uri and ref on @EndpointInject. Only one of them.
On Mon, Mar 15, 2010 at 10:21 AM, Tarjei Huse wrote:
>
>
>
> Claus Ibsen-2 wrote:
>>
>> Hi
>>
>> Use the ref component
>> http://camel.apache.org/ref
>>
>> from("ref:myRouteStart").process().to("ref:myRouteEnd");
>>
>>
>> Thanks
Claus Ibsen-2 wrote:
>
> Hi
>
> Use the ref component
> http://camel.apache.org/ref
>
> from("ref:myRouteStart").process().to("ref:myRouteEnd");
>
>
> Thanks. When I try this I get:
> org.apache.camel.FailedToCreateRouteException: Failed to create route
> Incomming to sourcechecker: Route[[
Hi,
Can this not be coded as 2 one-way interactions (sync=false) with the server
sending a response to a different socket (with a correlation id)...
Alternatively, I am sure if this has to be request/reply (to a given point)
you could also increase the connection keepAlive to ensure that the
con
Hi
Use the ref component
http://camel.apache.org/ref
from("ref:myRouteStart").process().to("ref:myRouteEnd");
On Mon, Mar 15, 2010 at 9:35 AM, Tarjei Huse wrote:
>
> Hi,
>
> if is possible to create a Route using from(Endpoint ep) or from("uri"), but
> I want to be able to register different e
Hi,
if is possible to create a Route using from(Endpoint ep) or from("uri"), but
I want to be able to register different endpoints in different situations
and let camel do the assigning for me. Is this possible?
The reason I want to do this, is to be able to create tests for routes where
I do
Hi Willem,
that is probably a good idea. I guess there are other modules that need
this setting too. I can report where I have failures now and you can
then also set these modules to fork per test.
Many modules like core and spring do not seem to need the setting. So I
guess it is a good idea
38 matches
Mail list logo