You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by mfeeney <mf...@tssg.org> on 2009/05/29 16:54:27 UTC
Re: Saxon Unsupported MEP : InOnly
HI,
I am using a Pipeline EIP in a Camel route builder class to accept a InOnly
MEP pass it through a Saxon SU and onto a Pojo SU and I still get ->
java.lang.UnsupportedOperationException: Unsupported MEP:
http://www.w3.org/2004
/08/wsdl/in-only
Pipeline Code -->
(SERVICE_IN_DB_UPDATE)
.pipeline(
"jbi:endpoint:http://domain/saxon/xslt-dynamic/Event",
"jbi:endpoint:http://domain/db/service/db");
How can this happen with a pipeline should it no be convert to an inout MEP
before entering the Saxon endpoint??
poilala wrote:
>
> Hi,
> I've a simple flow : Quartz -> Saxon(xslt transformaton) -> Http.
> When I try to deploy my package (with sm 3.1 or 3.2 snapshot from
> 03/05/07) I got the folowwing error :
> ERROR - SaxonComponent - Error processing exchange InOnly[
> id: ID:frecb000778-55755-1183468154627-12:1
> status: Active
> role: provider
> service: {http://www.blupblup.org}serviceName
> endpoint: endpointName
> in: <?xml version="1.0"
> encoding="UTF-8"?><timer><name>egdgd</name><group>dgdfg</group><fullname>dgdfg.egdgd</fullname><description/><fireTime>Tue
> Jul 03 15:10:23 CEST 2007</fireTime></timer>
> ]
> java.lang.UnsupportedOperationException: Unsupported MEP:
> http://www.w3.org/2004/08/wsdl/in-only
> at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.processInOnly(ProviderEndpoint.java:130)
> at
> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
> at
> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
> at
> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
> at
> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
> at
> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
> at
> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:595)
>
> I don't see how I could change the saxon component MEP neither why InOnly
> MEP isn't a right MEP.
>
> Could anyone help me ?
>
> Thanks
>
> Natahca
>
>
--
View this message in context: http://www.nabble.com/Saxon-Unsupported-MEP-%3A-InOnly-tp11412129p23781455.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Saxon Unsupported MEP : InOnly
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
Camel is bit less strict in its MEP handling than plain JBI. One
example: it can also use InOnly exchanges in a pipeline, reusing the
In message. As long you are using plain Camel, that's not a problem.
Whenever you send a MessageExchange to a JBI Endpoint, Camel will
default to the MEP it originally received. Your route probably
receives an InOnly exchange, so that's why Camel is now sending an
InOnly exchange to your Saxon XSLT endpoint. You can easily override
this default behavior by setting the preferred MEP on the endpoint
URI. In your case, using
jbi:endpoint:http://domain/saxon/xslt-dynamic/Event?mep=in-out should
do the trick.
Regards,
Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/
2009/5/29 mfeeney <mf...@tssg.org>:
>
> HI,
>
> I am using a Pipeline EIP in a Camel route builder class to accept a InOnly
> MEP pass it through a Saxon SU and onto a Pojo SU and I still get ->
>
> java.lang.UnsupportedOperationException: Unsupported MEP:
> http://www.w3.org/2004
> /08/wsdl/in-only
>
> Pipeline Code -->
>
> (SERVICE_IN_DB_UPDATE)
> .pipeline(
> "jbi:endpoint:http://domain/saxon/xslt-dynamic/Event",
> "jbi:endpoint:http://domain/db/service/db");
>
> How can this happen with a pipeline should it no be convert to an inout MEP
> before entering the Saxon endpoint??
>
>
>
> poilala wrote:
>>
>> Hi,
>> I've a simple flow : Quartz -> Saxon(xslt transformaton) -> Http.
>> When I try to deploy my package (with sm 3.1 or 3.2 snapshot from
>> 03/05/07) I got the folowwing error :
>> ERROR - SaxonComponent - Error processing exchange InOnly[
>> id: ID:frecb000778-55755-1183468154627-12:1
>> status: Active
>> role: provider
>> service: {http://www.blupblup.org}serviceName
>> endpoint: endpointName
>> in: <?xml version="1.0"
>> encoding="UTF-8"?><timer><name>egdgd</name><group>dgdfg</group><fullname>dgdfg.egdgd</fullname><description/><fireTime>Tue
>> Jul 03 15:10:23 CEST 2007</fireTime></timer>
>> ]
>> java.lang.UnsupportedOperationException: Unsupported MEP:
>> http://www.w3.org/2004/08/wsdl/in-only
>> at
>> org.apache.servicemix.common.endpoints.ProviderEndpoint.processInOnly(ProviderEndpoint.java:130)
>> at
>> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>> at
>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>> at
>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>> at
>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>> at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>> at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>> at java.lang.Thread.run(Thread.java:595)
>>
>> I don't see how I could change the saxon component MEP neither why InOnly
>> MEP isn't a right MEP.
>>
>> Could anyone help me ?
>>
>> Thanks
>>
>> Natahca
>>
>>
>
> --
> View this message in context: http://www.nabble.com/Saxon-Unsupported-MEP-%3A-InOnly-tp11412129p23781455.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
Re: Docs on creating BC
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Martin,
a good starting point is:
http://servicemix.apache.org/jbi-component-framework.html
You will find a section describing producer/consumer mode, etc.
You can see all existing binding components source code:
http://svn.apache.org/repos/asf/servicemix/components/bindings/
Concerning WSDL, it's a little bit more complex. Basicly, there is no
requirement for WSDL support. It means that most of binding components
don't support WSDL (like servicemix-file, servicemix-exec,
servicemix-smpp, etc).
Nevertheless, I have posted a message on the dev mailing list some weeks
ago to add basic WSDL support for all components. It's already in discuss :)
Regards
JB
Martin Feeney wrote:
> Hi all,
>
> Just in case I missed something I was wondering is there any extensive
> documentation out there on creating new BC providers and consumers that
> show good practice and WSDL extensions for endpoints.
>
> Many Thanks,
> Martin
>
> mfeeney wrote:
>> HI,
>>
>> I am using a Pipeline EIP in a Camel route builder class to accept a
>> InOnly
>> MEP pass it through a Saxon SU and onto a Pojo SU and I still get ->
>>
>> java.lang.UnsupportedOperationException: Unsupported MEP:
>> http://www.w3.org/2004
>> /08/wsdl/in-only
>>
>> Pipeline Code -->
>>
>> (SERVICE_IN_DB_UPDATE)
>> .pipeline(
>>
>> "jbi:endpoint:http://domain/saxon/xslt-dynamic/Event",
>> "jbi:endpoint:http://domain/db/service/db");
>>
>> How can this happen with a pipeline should it no be convert to an
>> inout MEP
>> before entering the Saxon endpoint??
>>
>>
>>
>> poilala wrote:
>>
>>> Hi,
>>> I've a simple flow : Quartz -> Saxon(xslt transformaton) -> Http.
>>> When I try to deploy my package (with sm 3.1 or 3.2 snapshot from
>>> 03/05/07) I got the folowwing error : ERROR -
>>> SaxonComponent - Error processing exchange InOnly[
>>> id: ID:frecb000778-55755-1183468154627-12:1
>>> status: Active
>>> role: provider
>>> service: {http://www.blupblup.org}serviceName
>>> endpoint: endpointName
>>> in: <?xml version="1.0"
>>> encoding="UTF-8"?><timer><name>egdgd</name><group>dgdfg</group><fullname>dgdfg.egdgd</fullname><description/><fireTime>Tue
>>>
>>> Jul 03 15:10:23 CEST 2007</fireTime></timer>
>>> ]
>>> java.lang.UnsupportedOperationException: Unsupported MEP:
>>> http://www.w3.org/2004/08/wsdl/in-only
>>> at
>>> org.apache.servicemix.common.endpoints.ProviderEndpoint.processInOnly(ProviderEndpoint.java:130)
>>>
>>> at
>>> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
>>>
>>> at
>>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>>>
>>> at
>>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>>>
>>> at
>>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>>>
>>> at
>>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>>>
>>> at
>>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>>>
>>> at
>>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>>>
>>> at
>>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>>>
>>> at
>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>>>
>>> at
>>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>>>
>>> at java.lang.Thread.run(Thread.java:595)
>>>
>>> I don't see how I could change the saxon component MEP neither why
>>> InOnly
>>> MEP isn't a right MEP.
>>>
>>> Could anyone help me ?
>>>
>>> Thanks
>>>
>>> Natahca
>>>
>>>
>>>
>>
>>
>
Docs on creating BC
Posted by Martin Feeney <mf...@tssg.org>.
Hi all,
Just in case I missed something I was wondering is there any extensive
documentation out there on creating new BC providers and consumers that
show good practice and WSDL extensions for endpoints.
Many Thanks,
Martin
mfeeney wrote:
> HI,
>
> I am using a Pipeline EIP in a Camel route builder class to accept a InOnly
> MEP pass it through a Saxon SU and onto a Pojo SU and I still get ->
>
> java.lang.UnsupportedOperationException: Unsupported MEP:
> http://www.w3.org/2004
> /08/wsdl/in-only
>
> Pipeline Code -->
>
> (SERVICE_IN_DB_UPDATE)
> .pipeline(
> "jbi:endpoint:http://domain/saxon/xslt-dynamic/Event",
> "jbi:endpoint:http://domain/db/service/db");
>
> How can this happen with a pipeline should it no be convert to an inout MEP
> before entering the Saxon endpoint??
>
>
>
> poilala wrote:
>
>> Hi,
>> I've a simple flow : Quartz -> Saxon(xslt transformaton) -> Http.
>> When I try to deploy my package (with sm 3.1 or 3.2 snapshot from
>> 03/05/07) I got the folowwing error :
>> ERROR - SaxonComponent - Error processing exchange InOnly[
>> id: ID:frecb000778-55755-1183468154627-12:1
>> status: Active
>> role: provider
>> service: {http://www.blupblup.org}serviceName
>> endpoint: endpointName
>> in: <?xml version="1.0"
>> encoding="UTF-8"?><timer><name>egdgd</name><group>dgdfg</group><fullname>dgdfg.egdgd</fullname><description/><fireTime>Tue
>> Jul 03 15:10:23 CEST 2007</fireTime></timer>
>> ]
>> java.lang.UnsupportedOperationException: Unsupported MEP:
>> http://www.w3.org/2004/08/wsdl/in-only
>> at
>> org.apache.servicemix.common.endpoints.ProviderEndpoint.processInOnly(ProviderEndpoint.java:130)
>> at
>> org.apache.servicemix.common.endpoints.ProviderEndpoint.process(ProviderEndpoint.java:100)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:489)
>> at
>> org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:441)
>> at
>> org.apache.servicemix.common.BaseLifeCycle.onMessageExchange(BaseLifeCycle.java:46)
>> at
>> org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:593)
>> at
>> org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:174)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:176)
>> at
>> org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
>> at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
>> at
>> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
>> at java.lang.Thread.run(Thread.java:595)
>>
>> I don't see how I could change the saxon component MEP neither why InOnly
>> MEP isn't a right MEP.
>>
>> Could anyone help me ?
>>
>> Thanks
>>
>> Natahca
>>
>>
>>
>
>
--
Research Software Developer
IMSARCS
Telecommunications Software & Systems Group (TSSG),
ArcLabs Research and Innovation Building,
Waterford Institute of Technology,
Carriganore Campus, Carriganore,
Co. Waterford, Ireland
www: www.tssg.org
Work: +353 (0)51 834020
Mobile: +353 (0)83 1463212
Work e-mail: mfeeney@tssg.org
Personal e-mail: martinfeeney@gmail.com
Skype: martinfeeney