Return-Path: Mailing-List: contact soap-user-help@xml.apache.org; run by ezmlm Delivered-To: mailing list soap-user@xml.apache.org Received: (qmail 89641 invoked from network); 26 Jun 2002 15:13:11 -0000 Received: from i1.genam.com (208.209.229.4) by 209.66.108.5 with SMTP; 26 Jun 2002 15:13:11 -0000 Subject: RE: Routing to Message Service To: soap-user@xml.apache.org From: JMaus@genam.com Date: Wed, 26 Jun 2002 10:16:44 -0500 Message-ID: X-MIMETrack: Serialize by Router on I1/GENAM(Release 5.0.8 |June 18, 2001) at 06/26/2002 10:15:29 AM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Rating: 209.66.108.5 1.6.2 0/1000/N -Dan, Yes; the following quick hack to the MessageRouterServlet.doPost() "wor= ks". The deployment description for our "urn:txlife-processor" is found and = my provider is invoked. Could this SOAPAction lookup make sense as a desired behavior for the s= tock Message Router? ... String targetID =3D e.getNamespaceURI (); if (targetID =3D=3D null) { // Check the SOAPAction for targetID (e.g., "urn:txlife-proces= sor"). targetID =3D req.getHeader("SOAPAction"); targetID =3D targetID.substring(1, targetID.length()-1); } String messageName =3D e.getLocalName (); // is this a valid message? dd =3D serviceManager.query (targetID); "Daniel P Allen" on 06/26/2002 08:23:59 AM Please respond to soap-user@xml.apache.org To: , cc: Subject: RE: Routing to Message Service =A0 The point is the Apache MessageRouter uses the first namespace declaration in the Body to find the service =A0=A0and Jim wants it to use SOAPAction instead.=A0 No can do with th= e stock MessageRouter.=A0 The code for =A0=A0message router is not long and is simple to understand,=A0 A qui= ck hack to change where it looks is almost =A0=A0trivial. A bit more difficult but still relatively simple would = be to check SOAPAction against the deployed =A0=A0services database and dispatch if a match is found.=A0 If no mat= ch then proceed with the stock behavior. =A0=A0This would eliminate the need for running two different servlets= if you are servicing "standard" Apache =A0=A0applications along with the ones Jim's folks are deploying.=A0 B= TW - the ebXML MessageService =A0 Specification also requires a different lookup mechanism.=A0 They = have added Service and Action =A0 elements to the header for this purpose but do not preclude use of= SOAPAction.. =A0 Dan -----Original Message----- From: Martin Gainty [mailto:mgainty@hotmail.com] Sent: Tuesday, June 25, 2002 6:25 PM To: soap-user@xml.apache.org Cc: JMaus@genam.com Subject: Re: Routing to Message Service Jim: Take a look at http://xml.apache.org/soap/docs/guide/rpcclient.html=A0f= or step by step building a RPC Client: Specifically Step 4 Set the target URI into the Call object using the setTargetObjectUR= I (...)method. Pass in the URN that the service used to identify itself in its deployment descriptor. (For Deployment Descriptors) Check out http://xmlapache.org/soap/docs/guide/deploy.html Standard Java Class Deployment Descriptor A deployment descriptor which exposes a service which is implemented vi= a a standard Java class (including a normal Java Bean) looks like the following: org.apache.soap.server.DOMFaultListener Where service-urn is the URN that you want to give to a service, exposed-methods is a space separated list of methods which you wish to= expose, and implementing-class is fully qualified class name (i.e. packagename.classname) that provides the methods which are being expos= ed I didnt see anything about SOAPAction here... Anyone else?? Martin Gainty > > >I have written a Message Services to pass a "TXLife" XML document cal= led "txlife-processor", deployed it, and have it working. But, the team writing >the client would like to use the SOAPAction to specify my "txlife-processor" messaging service (not xlmns=3D"urn:txlife-processor= "). >Is there a way to configure the SOAP Message Router to use the SOAPAc= tion (and not require xmlns=3D"urn:txlife-processor" attribute on my XML document) >to route the TXLife to my txlife-processor? >If SOAPAction is not appropriate, is there an alternative to requirin= g xmlns=3D"urn:txlife-processor" attribute on my TXLife element ? > >Following does not work: >... >SOAPAction: "urn:txlife-processor" > >>=3D"http://www.w3.org/2001/XMLSchema"> > > >... > >Following does work: >... >SOAPAction: "" > >>=3D"http://www.w3.org/2001/XMLSchema"> > > >... > >Thank you for your assistance. >-JimM > > > >-- >To unsubscribe, e-mail: >For additional commands, e-mail: Chat with friends online, try MSN Messenger: Click Here -- To unsubscribe, e-mail: For additional commands, e-mail: =