Yes, Saxon/XSLT SE supports InOut MEP only You can implement this using an eip pipeline component. quartz->pipeline(xslt->http) You can refer to the bridge sample for this.. <beans xmlns:eip="http://servicemix.apache.org/eip/1.0"; xmlns:b="http://servicemix.apache.org/samples/bridge";> <eip:pipeline service="b:pipeline" endpoint="endpoint"> <eip:transformer> <eip:exchange-target service="b:xslt" /> </eip:transformer> <eip:target> <eip:exchange-target service="b:http" /> </eip:target> </eip:pipeline> Regards, Rabi Mishra
________________________________ From: poilala [mailto:[EMAIL PROTECTED] Sent: Tue 7/3/2007 7:01 PM To: [email protected] Subject: Saxon Unsupported MEP : InOnly 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 <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-tf4018266s12049.html#a11412129 Sent from the ServiceMix - User mailing list archive at Nabble.com. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
