You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by "raulvk.soa" <ra...@gmail.com> on 2008/09/15 20:03:15 UTC
InOnly to InOut with JBI
Hi,
I am using Camel inside ServiceMix and I am getting an InOnly exchange on my
route.
However, I am trying to use a pipeline thereafter, to send the request to
several endpoints (validators, transformers, etc.), but I am getting an
error from the JBI Saxon Service Engine telling me that it does not support
the InOnly Exchange Pattern, which is only logical.
I am shocked as I would have thought that the Pipeline DSL construct in
Camel would send InOut exchanges all along except for the last endpoint
(which would be an InOnly)...
What is going on? How do I set the Exchange Pattern to InOut when invoking a
JBI Service???
My code is as follows:
from("jbi:service:http://www.company.org/ReceiveRequest")
.to("seda:processRequest");
from("seda:processRequest")
.pipeline("direct:transform1",
"direct:validate",
"direct:transform2",
"log:logging.category?level=INFO?showAll=true");
from("direct:transform1")
.to("jbi:service:http://www.company.org/Transform1");
from("direct:validate")
.to("validator:file:///d:/xxx/yyy.xsd");
from("direct:transform2")
.to("jbi:service:http://www.company.org/Transform2");
The error is being thrown when invoking
"jbi:service:http://www.company.org/Transform1". How do I tell Camel to send
out the Exchange as an InOut exchange?
Can someone please help?
Thanks.
--
View this message in context: http://www.nabble.com/InOnly-to-InOut-with-JBI-tp19498019s22882p19498019.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: InOnly to InOut with JBI
Posted by "raulvk.soa" <ra...@gmail.com>.
Thank you very much. It is very clear!
Raul.
Gert Vanthienen wrote:
>
> Raul,
>
> I just added it to the documentation this morning. It should be at
> http://activemq.apache.org/camel/jbi.html by now. Let me know if it's
> missing information you need.
> There also is a new FAQ entry to help people understand how to use this
> feature at
> http://activemq.apache.org/camel/how-do-i-set-the-mep-when-interacting-with-jbi.html.
>
> Regards,
>
> Gert
>
> raulvk.soa wrote:
>> Since this is not documented anywhere, can you please tell us what other
>> values the mep parameter accepts? Thank you.
>>
>>
>>
>> Gert Vanthienen wrote:
>>
>>> L.S.,
>>>
>>> You can specify the mep by appending it as a parameter the uri in this
>>> format ?mep=in-out.
>>> In your case, this becomes
>>> ...to("jbi:service:http://www.company.org/Transform1?mep=in-out");
>>>
>>> Regards,
>>>
>>> Gert
>>>
>>>
>>>> Hi,
>>>>
>>>> I am using Camel inside ServiceMix and I am getting an InOnly exchange
>>>> on
>>>> my
>>>> route.
>>>>
>>>> However, I am trying to use a pipeline thereafter, to send the request
>>>> to
>>>> several endpoints (validators, transformers, etc.), but I am getting an
>>>> error from the JBI Saxon Service Engine telling me that it does not
>>>> support
>>>> the InOnly Exchange Pattern, which is only logical.
>>>>
>>>> I am shocked as I would have thought that the Pipeline DSL construct in
>>>> Camel would send InOut exchanges all along except for the last endpoint
>>>> (which would be an InOnly)...
>>>>
>>>> What is going on? How do I set the Exchange Pattern to InOut when
>>>> invoking a
>>>> JBI Service???
>>>>
>>>> My code is as follows:
>>>>
>>>> from("jbi:service:http://www.company.org/ReceiveRequest")
>>>> .to("seda:processRequest");
>>>>
>>>> from("seda:processRequest")
>>>> .pipeline("direct:transform1",
>>>> "direct:validate",
>>>> "direct:transform2",
>>>>
>>>> "log:logging.category?level=INFO?showAll=true");
>>>>
>>>> from("direct:transform1")
>>>> .to("jbi:service:http://www.company.org/Transform1");
>>>>
>>>> from("direct:validate")
>>>> .to("validator:file:///d:/xxx/yyy.xsd");
>>>>
>>>> from("direct:transform2")
>>>> .to("jbi:service:http://www.company.org/Transform2");
>>>>
>>>>
>>>> The error is being thrown when invoking
>>>> "jbi:service:http://www.company.org/Transform1". How do I tell Camel to
>>>> send
>>>> out the Exchange as an InOut exchange?
>>>>
>>>> Can someone please help?
>>>>
>>>> Thanks.
>>>>
>>>>
>>>
>>> -----
>>> ---
>>> Gert Vanthienen
>>> http://www.anova.be
>>>
>>>
>>
>>
>
>
>
> -----
> ---
> Gert Vanthienen
> http://www.anova.be
>
--
View this message in context: http://www.nabble.com/InOnly-to-InOut-with-JBI-tp19498019s22882p19508337.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: InOnly to InOut with JBI
Posted by Gert Vanthienen <ge...@skynet.be>.
Raul,
I just added it to the documentation this morning. It should be at
http://activemq.apache.org/camel/jbi.html by now. Let me know if it's
missing information you need.
There also is a new FAQ entry to help people understand how to use this
feature at
http://activemq.apache.org/camel/how-do-i-set-the-mep-when-interacting-with-jbi.html.
Regards,
Gert
raulvk.soa wrote:
> Since this is not documented anywhere, can you please tell us what other
> values the mep parameter accepts? Thank you.
>
>
>
> Gert Vanthienen wrote:
>
>> L.S.,
>>
>> You can specify the mep by appending it as a parameter the uri in this
>> format ?mep=in-out.
>> In your case, this becomes
>> ...to("jbi:service:http://www.company.org/Transform1?mep=in-out");
>>
>> Regards,
>>
>> Gert
>>
>>
>>> Hi,
>>>
>>> I am using Camel inside ServiceMix and I am getting an InOnly exchange on
>>> my
>>> route.
>>>
>>> However, I am trying to use a pipeline thereafter, to send the request to
>>> several endpoints (validators, transformers, etc.), but I am getting an
>>> error from the JBI Saxon Service Engine telling me that it does not
>>> support
>>> the InOnly Exchange Pattern, which is only logical.
>>>
>>> I am shocked as I would have thought that the Pipeline DSL construct in
>>> Camel would send InOut exchanges all along except for the last endpoint
>>> (which would be an InOnly)...
>>>
>>> What is going on? How do I set the Exchange Pattern to InOut when
>>> invoking a
>>> JBI Service???
>>>
>>> My code is as follows:
>>>
>>> from("jbi:service:http://www.company.org/ReceiveRequest")
>>> .to("seda:processRequest");
>>>
>>> from("seda:processRequest")
>>> .pipeline("direct:transform1",
>>> "direct:validate",
>>> "direct:transform2",
>>>
>>> "log:logging.category?level=INFO?showAll=true");
>>>
>>> from("direct:transform1")
>>> .to("jbi:service:http://www.company.org/Transform1");
>>>
>>> from("direct:validate")
>>> .to("validator:file:///d:/xxx/yyy.xsd");
>>>
>>> from("direct:transform2")
>>> .to("jbi:service:http://www.company.org/Transform2");
>>>
>>>
>>> The error is being thrown when invoking
>>> "jbi:service:http://www.company.org/Transform1". How do I tell Camel to
>>> send
>>> out the Exchange as an InOut exchange?
>>>
>>> Can someone please help?
>>>
>>> Thanks.
>>>
>>>
>>
>> -----
>> ---
>> Gert Vanthienen
>> http://www.anova.be
>>
>>
>
>
RE: InOnly to InOut with JBI
Posted by Claus Ibsen <ci...@silverbullet.dk>.
Hi
Actually Gert was so kind that he documented it.
You can see the possible values:
http://activemq.apache.org/camel/jbi.html
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: raulvk.soa [mailto:raulvk.soa@gmail.com]
Sent: 16. september 2008 10:43
To: camel-user@activemq.apache.org
Subject: Re: InOnly to InOut with JBI
Since this is not documented anywhere, can you please tell us what other
values the mep parameter accepts? Thank you.
Gert Vanthienen wrote:
>
> L.S.,
>
> You can specify the mep by appending it as a parameter the uri in this
> format ?mep=in-out.
> In your case, this becomes
> ...to("jbi:service:http://www.company.org/Transform1?mep=in-out");
>
> Regards,
>
> Gert
>
>> Hi,
>>
>> I am using Camel inside ServiceMix and I am getting an InOnly exchange on
>> my
>> route.
>>
>> However, I am trying to use a pipeline thereafter, to send the request to
>> several endpoints (validators, transformers, etc.), but I am getting an
>> error from the JBI Saxon Service Engine telling me that it does not
>> support
>> the InOnly Exchange Pattern, which is only logical.
>>
>> I am shocked as I would have thought that the Pipeline DSL construct in
>> Camel would send InOut exchanges all along except for the last endpoint
>> (which would be an InOnly)...
>>
>> What is going on? How do I set the Exchange Pattern to InOut when
>> invoking a
>> JBI Service???
>>
>> My code is as follows:
>>
>> from("jbi:service:http://www.company.org/ReceiveRequest")
>> .to("seda:processRequest");
>>
>> from("seda:processRequest")
>> .pipeline("direct:transform1",
>> "direct:validate",
>> "direct:transform2",
>>
>> "log:logging.category?level=INFO?showAll=true");
>>
>> from("direct:transform1")
>> .to("jbi:service:http://www.company.org/Transform1");
>>
>> from("direct:validate")
>> .to("validator:file:///d:/xxx/yyy.xsd");
>>
>> from("direct:transform2")
>> .to("jbi:service:http://www.company.org/Transform2");
>>
>>
>> The error is being thrown when invoking
>> "jbi:service:http://www.company.org/Transform1". How do I tell Camel to
>> send
>> out the Exchange as an InOut exchange?
>>
>> Can someone please help?
>>
>> Thanks.
>>
>
>
>
> -----
> ---
> Gert Vanthienen
> http://www.anova.be
>
--
View this message in context: http://www.nabble.com/InOnly-to-InOut-with-JBI-tp19498019s22882p19507707.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: InOnly to InOut with JBI
Posted by "raulvk.soa" <ra...@gmail.com>.
Since this is not documented anywhere, can you please tell us what other
values the mep parameter accepts? Thank you.
Gert Vanthienen wrote:
>
> L.S.,
>
> You can specify the mep by appending it as a parameter the uri in this
> format ?mep=in-out.
> In your case, this becomes
> ...to("jbi:service:http://www.company.org/Transform1?mep=in-out");
>
> Regards,
>
> Gert
>
>> Hi,
>>
>> I am using Camel inside ServiceMix and I am getting an InOnly exchange on
>> my
>> route.
>>
>> However, I am trying to use a pipeline thereafter, to send the request to
>> several endpoints (validators, transformers, etc.), but I am getting an
>> error from the JBI Saxon Service Engine telling me that it does not
>> support
>> the InOnly Exchange Pattern, which is only logical.
>>
>> I am shocked as I would have thought that the Pipeline DSL construct in
>> Camel would send InOut exchanges all along except for the last endpoint
>> (which would be an InOnly)...
>>
>> What is going on? How do I set the Exchange Pattern to InOut when
>> invoking a
>> JBI Service???
>>
>> My code is as follows:
>>
>> from("jbi:service:http://www.company.org/ReceiveRequest")
>> .to("seda:processRequest");
>>
>> from("seda:processRequest")
>> .pipeline("direct:transform1",
>> "direct:validate",
>> "direct:transform2",
>>
>> "log:logging.category?level=INFO?showAll=true");
>>
>> from("direct:transform1")
>> .to("jbi:service:http://www.company.org/Transform1");
>>
>> from("direct:validate")
>> .to("validator:file:///d:/xxx/yyy.xsd");
>>
>> from("direct:transform2")
>> .to("jbi:service:http://www.company.org/Transform2");
>>
>>
>> The error is being thrown when invoking
>> "jbi:service:http://www.company.org/Transform1". How do I tell Camel to
>> send
>> out the Exchange as an InOut exchange?
>>
>> Can someone please help?
>>
>> Thanks.
>>
>
>
>
> -----
> ---
> Gert Vanthienen
> http://www.anova.be
>
--
View this message in context: http://www.nabble.com/InOnly-to-InOut-with-JBI-tp19498019s22882p19507707.html
Sent from the Camel - Users mailing list archive at Nabble.com.
RE: InOnly to InOut with JBI
Posted by Claus Ibsen <ci...@silverbullet.dk>.
Hi
Is the mep=xxx URI parameter option documented in a FAQ? That would be great if it were.
Med venlig hilsen
Claus Ibsen
......................................
Silverbullet
Skovsgårdsvænget 21
8362 Hørning
Tlf. +45 2962 7576
Web: www.silverbullet.dk
-----Original Message-----
From: Gert Vanthienen [mailto:gert.vanthienen@skynet.be]
Sent: 15. september 2008 20:15
To: camel-user@activemq.apache.org
Subject: Re: InOnly to InOut with JBI
L.S.,
You can specify the mep by appending it as a parameter the uri in this
format ?mep=in-out.
In your case, this becomes
...to("jbi:service:http://www.company.org/Transform1?mep=in-out");
Regards,
Gert
> Hi,
>
> I am using Camel inside ServiceMix and I am getting an InOnly exchange on my
> route.
>
> However, I am trying to use a pipeline thereafter, to send the request to
> several endpoints (validators, transformers, etc.), but I am getting an
> error from the JBI Saxon Service Engine telling me that it does not support
> the InOnly Exchange Pattern, which is only logical.
>
> I am shocked as I would have thought that the Pipeline DSL construct in
> Camel would send InOut exchanges all along except for the last endpoint
> (which would be an InOnly)...
>
> What is going on? How do I set the Exchange Pattern to InOut when invoking a
> JBI Service???
>
> My code is as follows:
>
> from("jbi:service:http://www.company.org/ReceiveRequest")
> .to("seda:processRequest");
>
> from("seda:processRequest")
> .pipeline("direct:transform1",
> "direct:validate",
> "direct:transform2",
>
> "log:logging.category?level=INFO?showAll=true");
>
> from("direct:transform1")
> .to("jbi:service:http://www.company.org/Transform1");
>
> from("direct:validate")
> .to("validator:file:///d:/xxx/yyy.xsd");
>
> from("direct:transform2")
> .to("jbi:service:http://www.company.org/Transform2");
>
>
> The error is being thrown when invoking
> "jbi:service:http://www.company.org/Transform1". How do I tell Camel to send
> out the Exchange as an InOut exchange?
>
> Can someone please help?
>
> Thanks.
>
Re: InOnly to InOut with JBI
Posted by Gert Vanthienen <ge...@skynet.be>.
L.S.,
You can specify the mep by appending it as a parameter the uri in this
format ?mep=in-out.
In your case, this becomes
...to("jbi:service:http://www.company.org/Transform1?mep=in-out");
Regards,
Gert
> Hi,
>
> I am using Camel inside ServiceMix and I am getting an InOnly exchange on my
> route.
>
> However, I am trying to use a pipeline thereafter, to send the request to
> several endpoints (validators, transformers, etc.), but I am getting an
> error from the JBI Saxon Service Engine telling me that it does not support
> the InOnly Exchange Pattern, which is only logical.
>
> I am shocked as I would have thought that the Pipeline DSL construct in
> Camel would send InOut exchanges all along except for the last endpoint
> (which would be an InOnly)...
>
> What is going on? How do I set the Exchange Pattern to InOut when invoking a
> JBI Service???
>
> My code is as follows:
>
> from("jbi:service:http://www.company.org/ReceiveRequest")
> .to("seda:processRequest");
>
> from("seda:processRequest")
> .pipeline("direct:transform1",
> "direct:validate",
> "direct:transform2",
>
> "log:logging.category?level=INFO?showAll=true");
>
> from("direct:transform1")
> .to("jbi:service:http://www.company.org/Transform1");
>
> from("direct:validate")
> .to("validator:file:///d:/xxx/yyy.xsd");
>
> from("direct:transform2")
> .to("jbi:service:http://www.company.org/Transform2");
>
>
> The error is being thrown when invoking
> "jbi:service:http://www.company.org/Transform1". How do I tell Camel to send
> out the Exchange as an InOut exchange?
>
> Can someone please help?
>
> Thanks.
>