From carlavasquez@example.net Tue Aug 1 03:20:10 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 52677 invoked from network); 1 Aug 2000 03:20:10 -0000 Received: from adsl-63-202-173-149.dsl.snfc21.pacbell.net (HELO zaks.demon.co.uk) (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 03:20:10 -0000 Received: from debian.simonfell.com ([83.161.120.155]) by zaks.demon.co.uk with SMTP (Mailtraq/83.161.120.1553) id ZKS1732F9776 for carlavasquez@example.net; Mon, 31 Jul 2000 20:19:29 -0700 From: Simon Fell <carlavasquez@example.net> To: carlavasquez@example.net Subject: Re: Soap return Values Date: Mon, 31 Jul 2000 20:19:29 -0700 Organization: c-call.com Message-ID: <carlavasquez@example.net> References: <carlavasquez@example.net> In-Reply-To: <carlavasquez@example.net> X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Hops: 1 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, 31 Jul 2000 12:08:47 -0400, in soap you wrote: >Does SOAP requires that every function should return a value. What if I = have a function that has an [in/out] parameter. That is if I have a = request like this > ><m:Increment xmlns:m=3D"Some-URI"> > <counter>1</counter> ></m:Increment> > >Would I be getting a response envelope simillar to following one or a = different one with return value? ><m:IncrementResponse xmlns:m=3D"Some-URI"> > <counter>2</counter> ></m:IncrementResponse> > >Thanx, >Kailash. > no, you are not required to have a return value. The example you give can map to either int Increment ( [in] int counter ) ; or void Increment ( [in/out] int * counter ) ; Cheers Simon From carlavasquez@example.net Tue Aug 1 04:39:25 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 66149 invoked from network); 1 Aug 2000 04:39:25 -0000 Received: from frog.walrus.com (HELO mailhub.walrus.com) (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 04:39:25 -0000 Received: from host (dialup-206-153-126-196.walrus.com [83.161.120.155]) by mailhub.walrus.com (8.9.2/8.8.6/ad) with SMTP id AAA25079; Tue, 1 Aug 2000 00:39:22 -0400 (EDT) Message-ID: <006901bffb72$659e9b40$021111c0@host> From: "John Hartman" <carlavasquez@example.net> To: <carlavasquez@example.net> Cc: "Sanjiva Weerawarana" <carlavasquez@example.net> Subject: Re: Error saving services registry: DeployedServices.ds Date: Tue, 1 Aug 2000 00:38:48 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Hello all: Has anyone else run across permission problems when using deploy.jsp? If not...well, Sanjiva...where is ServiceManager trying to write the registry to? I'm attempting to deploy the AddressFetcher "out of the box" so to speak, using the contents of DeploymentDescriptor.xml as my guide in completing the deployment. Submiting the form simply results in a server fault response. I've only been able to determine that the following exception occurs within org.apache.soap.server.ServiceManager (as indicated below in the stack trace I've included). I've installed JServ, running a relatively recent release of Apache, running on a Linux platform. Xerces and Soap are current up to July 26th. I've given world access to just about every directory I could guess the registry could be written to. Exception: [SOAPException: faultCode=SOAP-ENV:Server; msg=Error saving services registry: DeployedServices.ds (Permission denied)] [SOAPException: faultCode=SOAP-ENV:Server; msg=Error saving services registry: DeployedServices.ds (Permission denied)] at org.apache.soap.server.ServiceManager.saveRegistry(ServiceManager.java:127) at org.apache.soap.server.ServiceManager.deploy(ServiceManager.java:146) at jsp__soap__deploy_2ejsp._jspService(jsp__soap__deploy_2ejsp.java:154) at org.gjt.jsp.HttpJspPageImpl.service(HttpJspPageImpl.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.gjt.jsp.JspServlet$Page.process(JspServlet.java:908) at org.gjt.jsp.JspServlet.xservice(JspServlet.java:550) at org.gjt.jsp.JspServlet.service(JspServlet.java:436) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.apache.jserv.JServConnection.processRequest(JServConnection.java:317) at org.apache.jserv.JServConnection.run(JServConnection.java:188) at java.lang.Thread.run(Thread.java:475) From carlavasquez@example.net Tue Aug 1 12:43:07 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 84544 invoked from network); 1 Aug 2000 12:43:07 -0000 Received: from mplspop2.mpls.uswest.net (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 12:43:07 -0000 Received: (qmail 13656 invoked by alias); 1 Aug 2000 12:41:24 -0000 Delivered-To: carlavasquez@example.net@fixme Received: (qmail 11429 invoked by uid 0); 1 Aug 2000 12:39:57 -0000 Received: from pppdsle130.mpls.uswest.net (HELO pooh) (83.161.120.155) by mplspop2.mpls.uswest.net with SMTP; 1 Aug 2000 12:39:57 -0000 Reply-To: <carlavasquez@example.net> From: "Steven J. McDowall" <carlavasquez@example.net> To: <carlavasquez@example.net> Subject: RE: Error saving services registry: DeployedServices.ds Date: Tue, 1 Aug 2000 07:40:44 -0500 Message-ID: <carlavasquez@example.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <006901bffb72$659e9b40$021111c0@host> X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Well, for Tomcat it tries to store it in tomcat's bin directory.. :-) For Jserv I am sure it is also in a similar place.. (does Jserv have a bin dir too?) .. In effect, it is whereever the CWD happens to be at Jserv start up time.. -Steve -----Original Message----- From: John Hartman [mailto:carlavasquez@example.net] Sent: Monday, July 31, 2000 11:39 PM To: carlavasquez@example.net Cc: Sanjiva Weerawarana Subject: Re: Error saving services registry: DeployedServices.ds Hello all: Has anyone else run across permission problems when using deploy.jsp? If not...well, Sanjiva...where is ServiceManager trying to write the registry to? I'm attempting to deploy the AddressFetcher "out of the box" so to speak, using the contents of DeploymentDescriptor.xml as my guide in completing the deployment. Submiting the form simply results in a server fault response. I've only been able to determine that the following exception occurs within org.apache.soap.server.ServiceManager (as indicated below in the stack trace I've included). I've installed JServ, running a relatively recent release of Apache, running on a Linux platform. Xerces and Soap are current up to July 26th. I've given world access to just about every directory I could guess the registry could be written to. Exception: [SOAPException: faultCode=SOAP-ENV:Server; msg=Error saving services registry: DeployedServices.ds (Permission denied)] [SOAPException: faultCode=SOAP-ENV:Server; msg=Error saving services registry: DeployedServices.ds (Permission denied)] at org.apache.soap.server.ServiceManager.saveRegistry(ServiceManager.java:127) at org.apache.soap.server.ServiceManager.deploy(ServiceManager.java:146) at jsp__soap__deploy_2ejsp._jspService(jsp__soap__deploy_2ejsp.java:154) at org.gjt.jsp.HttpJspPageImpl.service(HttpJspPageImpl.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.gjt.jsp.JspServlet$Page.process(JspServlet.java:908) at org.gjt.jsp.JspServlet.xservice(JspServlet.java:550) at org.gjt.jsp.JspServlet.service(JspServlet.java:436) at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) at org.apache.jserv.JServConnection.processRequest(JServConnection.java:317) at org.apache.jserv.JServConnection.run(JServConnection.java:188) at java.lang.Thread.run(Thread.java:475) From carlavasquez@example.net Tue Aug 1 15:18:08 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 78765 invoked from network); 1 Aug 2000 15:18:08 -0000 Received: from dogbert.docspace.com (HELO torex01.docspace.com) (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 15:18:08 -0000 Received: from cp.net (83.161.120.155.on.wave.home.com [83.161.120.155]) by torex01.docspace.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 3M0QFLDK; Tue, 1 Aug 2000 11:20:25 -0400 Sender: bhorrock Message-ID: <carlavasquez@example.net> Date: Tue, 01 Aug 2000 11:17:38 -0400 From: Blaine Horrocks <carlavasquez@example.net> Organization: Critical Path, Inc. X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.15-4mdksmp i586) X-Accept-Language: en MIME-Version: 1.0 To: carlavasquez@example.net Subject: Re: Error saving services registry: DeployedServices.ds References: <carlavasquez@example.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N wrt Tomcat, I believe that the target directory is the startup directory for the jvm that tomcat runs in. Thus, for me, $TOMCAT_HOME is where the .ds file is placed because I start using bin/startup.sh. This is probably true for all other cases too. The start directory for the instance of the JVM running the soap code is where the file would be written. Cheers "Steven J. McDowall" wrote: > Well, for Tomcat it tries to store it in tomcat's bin directory.. :-) > > For Jserv I am sure it is also in a similar place.. (does Jserv have > a bin dir too?) .. > > In effect, it is whereever the CWD happens to be at Jserv start up time.. > > -Steve > > -----Original Message----- > From: John Hartman [mailto:carlavasquez@example.net] > Sent: Monday, July 31, 2000 11:39 PM > To: carlavasquez@example.net > Cc: Sanjiva Weerawarana > Subject: Re: Error saving services registry: DeployedServices.ds > > Hello all: > > Has anyone else run across permission problems when using deploy.jsp? If > not...well, Sanjiva...where is ServiceManager trying to write the registry > to? > > I'm attempting to deploy the AddressFetcher "out of the box" so to speak, > using the contents of DeploymentDescriptor.xml as my guide in completing the > deployment. Submiting the form simply results in a server fault response. > > I've only been able to determine that the following exception occurs within > org.apache.soap.server.ServiceManager (as indicated below in the stack trace > I've included). > > I've installed JServ, running a relatively recent release of Apache, running > on a Linux platform. Xerces and Soap are current up to July 26th. I've given > world access to just about every directory I could guess the registry could > be written to. > > Exception: [SOAPException: faultCode=SOAP-ENV:Server; msg=Error saving > services registry: DeployedServices.ds (Permission denied)] > [SOAPException: faultCode=SOAP-ENV:Server; msg=Error saving services > registry: DeployedServices.ds (Permission denied)] > at > org.apache.soap.server.ServiceManager.saveRegistry(ServiceManager.java:127) > at > org.apache.soap.server.ServiceManager.deploy(ServiceManager.java:146) > at > jsp__soap__deploy_2ejsp._jspService(jsp__soap__deploy_2ejsp.java:154) > at org.gjt.jsp.HttpJspPageImpl.service(HttpJspPageImpl.java:75) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) > at org.gjt.jsp.JspServlet$Page.process(JspServlet.java:908) > at org.gjt.jsp.JspServlet.xservice(JspServlet.java:550) > at org.gjt.jsp.JspServlet.service(JspServlet.java:436) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:588) > at > org.apache.jserv.JServConnection.processRequest(JServConnection.java:317) > at org.apache.jserv.JServConnection.run(JServConnection.java:188) > at java.lang.Thread.run(Thread.java:475) From carlavasquez@example.net Tue Aug 1 18:04:27 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 92151 invoked from network); 1 Aug 2000 18:04:27 -0000 Received: from smtp2.exe.com (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 18:04:27 -0000 Received: from notesmaildal.exe.com (notesmaildal.exe.com [83.161.120.155]) by smtp2.exe.com (8.9.3/8.9.3) with SMTP id NAA25943 for <carlavasquez@example.net>; Tue, 1 Aug 2000 13:03:58 -0500 Received: by notesmaildal.exe.com(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id 8625692E.00631267 ; Tue, 1 Aug 2000 13:02:07 -0500 X-Lotus-FromDomain: EXE From: carlavasquez@example.net To: carlavasquez@example.net Message-ID: <carlavasquez@example.net> Date: Tue, 1 Aug 2000 13:02:02 -0500 Subject: Re: C++ Implementation Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Actually, my partner has just about finished a hot-pluggable loading system (think of it as a very very stripped down version of COM without a lot of the baggage that has no prerequisites and compiles everywhere (well, everywhere that has dlopen(), etc, which is pretty much everywhere in UNIXland)) that with a very little tweaking could make a nice lightweight C++ servlet engine. We'd be happy to do some tweaking and submit it for SOAP use if it would be useful... Unless someone else already has one? The only real additions needed would be the configurable assignment of DLLs to URLs, but that's not that big of a deal. You'd then just right your servlet (or more likely an IDL-to-C++ script would) with a couple of well-known methods containing pointers to the specific methods implemented, compile it as a DLL, and put it into a given directory (or one of many, classpath style). Interested? -Richard carlavasquez@example.net on 07/31/2000 02:03:27 PM Please respond to carlavasquez@example.net To: carlavasquez@example.net cc: (bcc: Richard Stanford/EXE) Subject: Re: C++ Implementation Ricard Stanford wrote: > > If there's not much interest in a standalone SOAP-handler, I'll probably > end up going with Apache, but in a lot of ways it seems to be overkill. > Especially for adding SOAP support to preexisting server applications, > that's the main reason I haven't done much with the Java version to date. > I really want to avoid rolling my own stuff for this, however. Thoughts? If someone donates code that runs standalone, then I'll wager that shortly somebody else will donate code that hooks this to Apache, and somebody (else?) will donate code that integrates it with IIS... At least that's how it went with Tomcat (which originally was a standalone Java servlet engine). All we need is somebody to plant the seed. - Sam Ruby From carlavasquez@example.net Tue Aug 1 18:22:01 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 9687 invoked from network); 1 Aug 2000 18:22:01 -0000 Received: from mail.xmls.com (HELO NEW.xmlsmail.xmls.com) (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 18:22:01 -0000 Received: by NEW.xmlsmail.xmls.com with Internet Mail Service (5.5.2650.21) id <QABK6L33>; Tue, 1 Aug 2000 14:22:00 -0400 Message-ID: <carlavasquez@example.net> From: Kevin Mitchell <carlavasquez@example.net> To: "'carlavasquez@example.net'" <carlavasquez@example.net> Subject: RE: cvs commit: xml-soap/java/src/org/apache/soap/util/net HTTPUt ils.java Date: Tue, 1 Aug 2000 14:21:59 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Sorry for the delay getting to this, but w/r/t the test mentioned below, everything checked out OK. I ran a successful test of a SOAP RPC from an Intel SOAP client to a SPARC SOAP server and vice versa. ~kjm -----Original Message----- From: Kevin J. Mitchell [mailto:carlavasquez@example.net] Sent: Friday, July 14, 2000 9:48 AM To: carlavasquez@example.net Subject: RE: cvs commit: xml-soap/java/src/org/apache/soap/util/net HTTPUtils.java From what I gather, Java is a big-endian (i.e. most significant byte first) and therefore also network-byte-order oriented (i.e. like TCP/IP). The big-endian/little-endian problem typically comes up when reading data from disk... See the following URL for an example (go to Question 11).. http://java.sun.com/people/linden/faq_b2.html#I/O However, it does make me more than a little nervous. I will conduct a test with Intel client/SPARC server and vice versa and post the results... But, the fix does get us further, and I think we should move forward with it... -----Original Message----- From: Sanjiva Weerawarana [mailto:carlavasquez@example.net] Sent: Friday, July 14, 2000 12:46 AM To: carlavasquez@example.net Subject: Re: cvs commit: xml-soap/java/src/org/apache/soap/util/net HTTPUtils.java > I am also not sure about the endian problem! I would very much like to see a > stream and not print based output, the current implementation IMHO is not very > well structured in this respect.... (- Could you expand on this a bit? I'm not sure I understand what you meant by stream vs. print. The current implementation could definitely do with major restructuring. I think at least the following are essential: - use SAX at the lower level - expose a messaging API and a management framework for it - expose an RPC API and a management framework for it (this is pretty much what the current code does) - sort out the lifecycle management stuff in a transport-independent manner - set up for better integration to different transports - the serializer/deserializer stuff needs re-thinking All of this needs to be done without blowing up the code size needlessly. I hope that the next major rev of this codebase will tackle some of these issues .. it of course depends on the degree of community participation! Sanjiva. From carlavasquez@example.net Tue Aug 1 18:23:31 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 10743 invoked from network); 1 Aug 2000 18:23:31 -0000 Received: from smtp-out001.onemain.com (HELO mail006.mail.onemain.com) (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 18:23:31 -0000 Received: (qmail 5798 invoked from network); 1 Aug 2000 18:23:03 -0000 Received: from unknown (HELO ibs?10.THE?MOON) ([83.161.120.155]) (envelope-sender <carlavasquez@example.net>) by mail006.mail.onemain.com (qmail-ldap-1.03) with SMTP for <carlavasquez@example.net>; 1 Aug 2000 18:23:03 -0000 Received: by IBS_10 with Internet Mail Service (5.5.2650.21) id <QB94NKYG>; Tue, 1 Aug 2000 11:18:26 -0700 Message-ID: <712324ACD27BD011B17C0080AD17D38A1B5D63@IBS_10> From: James Snell <carlavasquez@example.net> To: "'carlavasquez@example.net'" <carlavasquez@example.net> Subject: RE: C++ Implementation Date: Tue, 1 Aug 2000 11:18:21 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N This sounds very interesting. I think I'd like to see what you've put together... could ya send it over to me for a peek? - James -----Original Message----- From: carlavasquez@example.net [mailto:carlavasquez@example.net] Sent: Tuesday, August 01, 2000 11:02 AM To: carlavasquez@example.net Subject: Re: C++ Implementation Actually, my partner has just about finished a hot-pluggable loading system (think of it as a very very stripped down version of COM without a lot of the baggage that has no prerequisites and compiles everywhere (well, everywhere that has dlopen(), etc, which is pretty much everywhere in UNIXland)) that with a very little tweaking could make a nice lightweight C++ servlet engine. We'd be happy to do some tweaking and submit it for SOAP use if it would be useful... Unless someone else already has one? The only real additions needed would be the configurable assignment of DLLs to URLs, but that's not that big of a deal. You'd then just right your servlet (or more likely an IDL-to-C++ script would) with a couple of well-known methods containing pointers to the specific methods implemented, compile it as a DLL, and put it into a given directory (or one of many, classpath style). Interested? -Richard carlavasquez@example.net on 07/31/2000 02:03:27 PM Please respond to carlavasquez@example.net To: carlavasquez@example.net cc: (bcc: Richard Stanford/EXE) Subject: Re: C++ Implementation Ricard Stanford wrote: > > If there's not much interest in a standalone SOAP-handler, I'll probably > end up going with Apache, but in a lot of ways it seems to be overkill. > Especially for adding SOAP support to preexisting server applications, > that's the main reason I haven't done much with the Java version to date. > I really want to avoid rolling my own stuff for this, however. Thoughts? If someone donates code that runs standalone, then I'll wager that shortly somebody else will donate code that hooks this to Apache, and somebody (else?) will donate code that integrates it with IIS... At least that's how it went with Tomcat (which originally was a standalone Java servlet engine). All we need is somebody to plant the seed. - Sam Ruby From carlavasquez@example.net Tue Aug 1 19:46:29 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 64354 invoked by uid 500); 1 Aug 2000 19:46:29 -0000 Delivered-To: carlavasquez@example.net Received: (qmail 64347 invoked by uid 1137); 1 Aug 2000 19:46:28 -0000 Date: 1 Aug 2000 19:46:28 -0000 Message-ID: <carlavasquez@example.net> From: carlavasquez@example.net To: carlavasquez@example.net Subject: cvs commit: xml-soap/java/src/org/apache/soap/server DeploymentDescriptor.java ServiceManager.java ServiceManagerClient.java duftler 00/08/01 12:46:28 Modified: java/src/org/apache/soap Constants.java java/src/org/apache/soap/rpc RPCConstants.java java/src/org/apache/soap/server DeploymentDescriptor.java ServiceManager.java ServiceManagerClient.java Log: Changed some overlooked IBM-SOAP references to XML-SOAP. Thanks to Mike Paolini (carlavasquez@example.net) for pointing these out. Revision Changes Path 1.6 +2 -2 xml-soap/java/src/org/apache/soap/Constants.java Index: Constants.java =================================================================== RCS file: /home/cvs/xml-soap/java/src/org/apache/soap/Constants.java,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- Constants.java 2000/07/28 11:40:47 1.5 +++ Constants.java 2000/08/01 19:46:21 1.6 @@ -86,9 +86,9 @@ "http://www.w3.org/1999/XMLSchema-instance"; public static String NS_URI_SCHEMA_XSD = "http://www.w3.org/1999/XMLSchema"; - public static String NS_URI_IBM_SOAP = + public static String NS_URI_XML_SOAP = "http://xml.apache.org/xml-soap"; - public static String NS_URI_IBM_DEPLOYMENT = + public static String NS_URI_XML_SOAP_DEPLOYMENT = "http://xml.apache.org/xml-soap/deployment"; public static String NS_URI_LITERAL_XML = "http://xml.apache.org/xml-soap/literalxml"; 1.3 +1 -1 xml-soap/java/src/org/apache/soap/rpc/RPCConstants.java Index: RPCConstants.java =================================================================== RCS file: /home/cvs/xml-soap/java/src/org/apache/soap/rpc/RPCConstants.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- RPCConstants.java 2000/05/30 10:24:01 1.2 +++ RPCConstants.java 2000/08/01 19:46:22 1.3 @@ -79,7 +79,7 @@ // Other constants. public static String RESPONSE_SUFFIX = "Response"; - // IBM implementation defined fault codes. + // XML-SOAP implementation defined fault codes. public static String FAULT_CODE_SERVER_BAD_TARGET_OBJECT_URI = Constants.FAULT_CODE_SERVER + ".BadTargetObjectURI"; } 1.4 +10 -8 xml-soap/java/src/org/apache/soap/server/DeploymentDescriptor.java Index: DeploymentDescriptor.java =================================================================== RCS file: /home/cvs/xml-soap/java/src/org/apache/soap/server/DeploymentDescriptor.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- DeploymentDescriptor.java 2000/07/20 14:37:43 1.3 +++ DeploymentDescriptor.java 2000/08/01 19:46:24 1.4 @@ -220,7 +220,7 @@ PrintWriter pw = new PrintWriter (pr); pw.println ("<isd:service xmlns:isd=\"" + - Constants.NS_URI_IBM_DEPLOYMENT + "\" id=\"" + id + "\">"); + Constants.NS_URI_XML_SOAP_DEPLOYMENT + "\" id=\"" + id + "\">"); byte pt = providerType; String[] scopes = {"Page", "Request", "Session", "Application"}; @@ -280,11 +280,11 @@ */ public static DeploymentDescriptor fromXML (Element root) { if ((root == null) || - !root.getNamespaceURI().equals (Constants.NS_URI_IBM_DEPLOYMENT) || + !root.getNamespaceURI().equals (Constants.NS_URI_XML_SOAP_DEPLOYMENT) || !root.getLocalName().equals ("service")) { throw new IllegalArgumentException ("root is null or document element " + "is not {" + - Constants.NS_URI_IBM_DEPLOYMENT + + Constants.NS_URI_XML_SOAP_DEPLOYMENT + "}service"); } @@ -299,7 +299,7 @@ } dd.setID (id); - nl = root.getElementsByTagNameNS (Constants.NS_URI_IBM_DEPLOYMENT, + nl = root.getElementsByTagNameNS (Constants.NS_URI_XML_SOAP_DEPLOYMENT, "provider"); if ((nl == null) || nl.getLength () != 1) { throw new IllegalArgumentException ("exactly one 'provider' element " + @@ -325,7 +325,8 @@ if (typeStr.equals ("java")) { dd.setProviderType (DeploymentDescriptor.PROVIDER_JAVA); - nl = e.getElementsByTagNameNS (Constants.NS_URI_IBM_DEPLOYMENT, "java"); + nl = e.getElementsByTagNameNS (Constants.NS_URI_XML_SOAP_DEPLOYMENT, + "java"); if ((nl == null) || nl.getLength () != 1) { throw new IllegalArgumentException ("exactly one 'java' element " + "missing in deployment " + @@ -354,7 +355,7 @@ dd.setIsStatic (isStaticBool); } else { - nl = e.getElementsByTagNameNS (Constants.NS_URI_IBM_DEPLOYMENT, + nl = e.getElementsByTagNameNS (Constants.NS_URI_XML_SOAP_DEPLOYMENT, "script"); if ((nl == null) || nl.getLength () != 1) { throw new IllegalArgumentException ("exactly one 'script' element " + @@ -393,7 +394,7 @@ dd.setMethods (methods); // read the type mappings - nl = root.getElementsByTagNameNS (Constants.NS_URI_IBM_DEPLOYMENT, + nl = root.getElementsByTagNameNS (Constants.NS_URI_XML_SOAP_DEPLOYMENT, "mappings"); if ((nl == null) || nl.getLength () > 1) { throw new IllegalArgumentException ("at most one 'mappings' element " + @@ -401,7 +402,8 @@ } if (nl.getLength () == 1) { e = (Element) nl.item (0); - nl = e.getElementsByTagNameNS (Constants.NS_URI_IBM_DEPLOYMENT, "map"); + nl = e.getElementsByTagNameNS (Constants.NS_URI_XML_SOAP_DEPLOYMENT, + "map"); int nmaps = nl.getLength (); if (nmaps > 0) { TypeMapping[] tms = new TypeMapping[nmaps]; 1.3 +2 -2 xml-soap/java/src/org/apache/soap/server/ServiceManager.java Index: ServiceManager.java =================================================================== RCS file: /home/cvs/xml-soap/java/src/org/apache/soap/server/ServiceManager.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ServiceManager.java 2000/05/30 10:24:05 1.2 +++ ServiceManager.java 2000/08/01 19:46:25 1.3 @@ -89,13 +89,13 @@ // objects smsdd.setMappings (new TypeMapping[] { new TypeMapping (Constants.NS_URI_SOAP_ENC, - new QName (Constants.NS_URI_IBM_SOAP, + new QName (Constants.NS_URI_XML_SOAP, "DeploymentDescriptor"), "org.apache.soap.server.DeploymentDescriptor", "org.apache.soap.encoding.soapenc.BeanSerializer", "org.apache.soap.encoding.soapenc.BeanSerializer"), new TypeMapping (Constants.NS_URI_SOAP_ENC, - new QName (Constants.NS_URI_IBM_SOAP, + new QName (Constants.NS_URI_XML_SOAP, "TypeMapping"), "org.apache.soap.server.TypeMapping", "org.apache.soap.server.TypeMappingSerializer", 1.4 +4 -4 xml-soap/java/src/org/apache/soap/server/ServiceManagerClient.java Index: ServiceManagerClient.java =================================================================== RCS file: /home/cvs/xml-soap/java/src/org/apache/soap/server/ServiceManagerClient.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- ServiceManagerClient.java 2000/07/20 17:24:53 1.3 +++ ServiceManagerClient.java 2000/08/01 19:46:25 1.4 @@ -67,7 +67,7 @@ import org.apache.soap.rpc.*; /** - * This is a client to talk to a IBM-SOAP ServiceManager to manage services + * This is a client to talk to an XML-SOAP ServiceManager to manage services * deployed on the server. * * @author Sanjiva Weerawarana (carlavasquez@example.net) @@ -86,12 +86,12 @@ // register serializer/deserializer for DeploymentDescriptor.class // and TypeMapping.class smr.mapTypes (Constants.NS_URI_SOAP_ENC, - new QName (Constants.NS_URI_IBM_SOAP, + new QName (Constants.NS_URI_XML_SOAP, "DeploymentDescriptor"), DeploymentDescriptor.class, bs, (Deserializer) bs); bs = new TypeMappingSerializer (); smr.mapTypes (Constants.NS_URI_SOAP_ENC, - new QName (Constants.NS_URI_IBM_SOAP, "TypeMapping"), + new QName (Constants.NS_URI_XML_SOAP, "TypeMapping"), TypeMapping.class, bs, (Deserializer) bs); } @@ -154,7 +154,7 @@ ServiceManagerClient.class.getName () + " url operation arguments"); System.err.println ("where"); - System.err.println ("\turl is the IBM-SOAP router's URL whose services" + + System.err.println ("\turl is the XML-SOAP router's URL whose services" + " are managed"); System.err.println ("\toperation and arguments are:"); System.err.println ("\t\tdeploy deployment-descriptor-file.xml"); From carlavasquez@example.net Tue Aug 1 20:20:17 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 82786 invoked from network); 1 Aug 2000 20:20:17 -0000 Received: from d06lmsgate-3.uk.ibm.com (HELO d06lmsgate-3.emea.ibm.com) (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 20:20:17 -0000 Received: from d06relay01.portsmouth.uk.ibm.com (d06relay01.portsmouth.uk.ibm.com [83.161.120.155]) by d06lmsgate-3.emea.ibm.com (1.0.0) with ESMTP id VAA151594 for <carlavasquez@example.net>; Tue, 1 Aug 2000 21:11:54 +0100 Received: from gnkhelp308.greenock.uk.ibm.com (gnkhelp308.greenock.uk.ibm.com [83.161.120.155]) by d06relay01.portsmouth.uk.ibm.com (8.8.8m3/NCO v4.92) with ESMTP id VAA75722 for <carlavasquez@example.net>; Tue, 1 Aug 2000 21:19:49 +0100 Received: from roadkill.rchland.ibm.com (roadkill.rchland.ibm.com [83.161.120.155]) by gnkhelp308.greenock.uk.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with SMTP id UAA28014 for <carlavasquez@example.net>; Tue, 1 Aug 2000 20:18:33 GMT Message-Id: <carlavasquez@example.net> From: "Wouter Cloetens" <carlavasquez@example.net> To: "carlavasquez@example.net" <carlavasquez@example.net> Date: Tue, 01 Aug 2000 15:18:44 +0600 Reply-To: "Wouter Cloetens" <carlavasquez@example.net> Priority: Normal X-Mailer: PMMail 1.96a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: cvs commit: xml-soap/java/src/org/apache/soap/server DeploymentDescriptor.java ServiceManager.java ServiceManagerClient.java X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On 1 Aug 2000 19:46:28 -0000, carlavasquez@example.net wrote: > - public static String NS_URI_IBM_SOAP = > + public static String NS_URI_XML_SOAP = While you're taking out references to IBM, take out these too: - Calculator.java: "IBM-SOAP Calculator" - the "IBM-SOAP" admin banner gif - ServerConstants.java: "urn:ibm-soap-service-management-service" - ServiceManagerClient.java: "url is the IBM-SOAP router's URL" By the way, although the tunnel is a very useful tool, I'm not sure if it should be part of the org.apache.soap hierarchy. It logically has nothing to do with SOAP... bfn, Wouter From carlavasquez@example.net Tue Aug 1 21:18:39 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 11035 invoked by uid 500); 1 Aug 2000 21:18:39 -0000 Delivered-To: carlavasquez@example.net Received: (qmail 11031 invoked by uid 1137); 1 Aug 2000 21:18:38 -0000 Date: 1 Aug 2000 21:18:38 -0000 Message-ID: <carlavasquez@example.net> From: carlavasquez@example.net To: carlavasquez@example.net Subject: cvs commit: xml-soap/java/webapps/admin soapadmin.gif duftler 00/08/01 14:18:38 Modified: java/samples/addressbook DeploymentDescriptor.xml GetAddress.java PutAddress.java README java/samples/calculator Calculator.java DeploymentDescriptor.xml README java/samples/stockquote GetQuote.java GetQuoteSMTP.java README java/src/org/apache/soap/server ServerConstants.java java/webapps/admin soapadmin.gif Log: Changed some more IBM-SOAP references to XML-SOAP. Thanks to Wouter Cloetens (carlavasquez@example.net) for pointing some of these out. Revision Changes Path 1.6 +2 -2 xml-soap/java/samples/addressbook/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/DeploymentDescriptor.xml,v retrieving revision 1.5 retrieving revision 1.6 diff -u -r1.5 -r1.6 --- DeploymentDescriptor.xml 2000/06/02 09:41:31 1.5 +++ DeploymentDescriptor.xml 2000/08/01 21:18:31 1.6 @@ -7,12 +7,12 @@ </isd:provider> <isd:mappings> <isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" - xmlns:x="urn:ibm-soap-address-demo" qname="x:address" + xmlns:x="urn:xml-soap-address-demo" qname="x:address" javaType="samples.addressbook.Address" java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer" xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/> <isd:map encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" - xmlns:x="urn:ibm-soap-address-demo" qname="x:phone" + xmlns:x="urn:xml-soap-address-demo" qname="x:phone" javaType="samples.addressbook.PhoneNumber" java2XMLClassName="org.apache.soap.encoding.soapenc.BeanSerializer" xml2JavaClassName="org.apache.soap.encoding.soapenc.BeanSerializer"/> 1.4 +2 -2 xml-soap/java/samples/addressbook/GetAddress.java Index: GetAddress.java =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/GetAddress.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- GetAddress.java 2000/05/30 10:23:39 1.3 +++ GetAddress.java 2000/08/01 21:18:31 1.4 @@ -97,10 +97,10 @@ // Map the types. smr.mapTypes(Constants.NS_URI_SOAP_ENC, - new QName("urn:ibm-soap-address-demo", "address"), + new QName("urn:xml-soap-address-demo", "address"), Address.class, beanSer, beanSer); smr.mapTypes(Constants.NS_URI_SOAP_ENC, - new QName("urn:ibm-soap-address-demo", "phone"), + new QName("urn:xml-soap-address-demo", "phone"), PhoneNumber.class, beanSer, beanSer); // Build the call. 1.4 +2 -2 xml-soap/java/samples/addressbook/PutAddress.java Index: PutAddress.java =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/PutAddress.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- PutAddress.java 2000/05/30 10:23:40 1.3 +++ PutAddress.java 2000/08/01 21:18:31 1.4 @@ -109,10 +109,10 @@ // Map the types. smr.mapTypes(Constants.NS_URI_SOAP_ENC, - new QName("urn:ibm-soap-address-demo", "address"), + new QName("urn:xml-soap-address-demo", "address"), Address.class, beanSer, beanSer); smr.mapTypes(Constants.NS_URI_SOAP_ENC, - new QName("urn:ibm-soap-address-demo", "phone"), + new QName("urn:xml-soap-address-demo", "phone"), PhoneNumber.class, beanSer, beanSer); // Build the call. 1.4 +3 -3 xml-soap/java/samples/addressbook/README Index: README =================================================================== RCS file: /home/cvs/xml-soap/java/samples/addressbook/README,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- README 2000/06/02 09:41:31 1.3 +++ README 2000/08/01 21:18:31 1.4 @@ -2,8 +2,8 @@ Service: ------- -To install this service on a IBM-SOAP listener, you need to make -the samples.addressbook package available on the IBM-SOAP listener's +To install this service on a XML-SOAP listener, you need to make +the samples.addressbook package available on the XML-SOAP listener's classpath. Then deploy this service by filling in the deployment template using the info in the deployment descriptor in this directory. @@ -40,4 +40,4 @@ ------------ java samples.addressbook.GetAddress \ - http://localhost:2020/ibm-soap/rpcrouter.jsp "John B. Good" + http://localhost:2020/xml-soap/rpcrouter.jsp "John B. Good" 1.4 +3 -3 xml-soap/java/samples/calculator/Calculator.java Index: Calculator.java =================================================================== RCS file: /home/cvs/xml-soap/java/samples/calculator/Calculator.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- Calculator.java 2000/05/30 10:23:44 1.3 +++ Calculator.java 2000/08/01 21:18:33 1.4 @@ -204,7 +204,7 @@ throws SOAPException { // Build the call. Call call = new Call (); - call.setTargetObjectURI ("urn:ibm-soap-demo-calculator"); + call.setTargetObjectURI ("urn:xml-soap-demo-calculator"); call.setMethodName (op); call.setEncodingStyleURI(encodingStyleURI); Vector params = new Vector (); @@ -215,7 +215,7 @@ call.setParams (params); // make the call: note that the action URI is empty because the - // IBM-SOAP rpc router does not need this. This may change in the + // XML-SOAP rpc router does not need this. This may change in the // future. Response resp = call.invoke (/* router URL */ url, /* actionURI */ "" ); @@ -258,7 +258,7 @@ System.exit (1); } - Calculator c = new Calculator ("IBM-SOAP Calculator"); + Calculator c = new Calculator ("XML-SOAP Calculator"); int offset = maxargs - args.length; c.encodingStyleURI = (args.length == maxargs) 1.4 +1 -1 xml-soap/java/samples/calculator/DeploymentDescriptor.xml Index: DeploymentDescriptor.xml =================================================================== RCS file: /home/cvs/xml-soap/java/samples/calculator/DeploymentDescriptor.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- DeploymentDescriptor.xml 2000/06/01 19:37:57 1.3 +++ DeploymentDescriptor.xml 2000/08/01 21:18:33 1.4 @@ -1,7 +1,7 @@ <?xml version="1.0"?> <isd:service xmlns:isd="http://xml.apache.org/xml-soap/deployment" - id="urn:ibm-soap-demo-calculator"> + id="urn:xml-soap-demo-calculator"> <isd:provider type="script" scope="Application" methods="plus minus times divide"> 1.3 +3 -3 xml-soap/java/samples/calculator/README Index: README =================================================================== RCS file: /home/cvs/xml-soap/java/samples/calculator/README,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- README 2000/05/30 10:23:44 1.2 +++ README 2000/08/01 21:18:33 1.3 @@ -2,8 +2,8 @@ Service: ------- -To install this service on a IBM-SOAP listener, you need to make -the samples.addressbook package available on the IBM-SOAP listener's +To install this service on a XML-SOAP listener, you need to make +the samples.addressbook package available on the XML-SOAP listener's classpath. Then deploy this service by filling in the deployment template using the info in the deployment descriptor in this directory or by using the service manager client: @@ -38,4 +38,4 @@ ------------ java samples.calculator.Calculator \ - http://localhost:2020/ibm-soap/rpcrouter.jsp + http://localhost:2020/xml-soap/rpcrouter.jsp 1.4 +1 -1 xml-soap/java/samples/stockquote/GetQuote.java Index: GetQuote.java =================================================================== RCS file: /home/cvs/xml-soap/java/samples/stockquote/GetQuote.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- GetQuote.java 2000/05/30 10:23:46 1.3 +++ GetQuote.java 2000/08/01 21:18:36 1.4 @@ -98,7 +98,7 @@ call.setParams (params); // make the call: note that the action URI is empty because the - // IBM-SOAP rpc router does not need this. This may change in the + // XML-SOAP rpc router does not need this. This may change in the // future. Response resp = call.invoke (/* router URL */ url, /* actionURI */ "" ); 1.4 +1 -1 xml-soap/java/samples/stockquote/GetQuoteSMTP.java Index: GetQuoteSMTP.java =================================================================== RCS file: /home/cvs/xml-soap/java/samples/stockquote/GetQuoteSMTP.java,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- GetQuoteSMTP.java 2000/05/30 10:23:46 1.3 +++ GetQuoteSMTP.java 2000/08/01 21:18:36 1.4 @@ -126,7 +126,7 @@ call.setParams (params); // make the call: note that the action URI is empty because the - // IBM-SOAP rpc router does not need this. This may change in the + // XML-SOAP rpc router does not need this. This may change in the // future. Response resp = call.invoke (/* router URL */ url, /* actionURI */ "" ); 1.3 +3 -3 xml-soap/java/samples/stockquote/README Index: README =================================================================== RCS file: /home/cvs/xml-soap/java/samples/stockquote/README,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- README 2000/05/30 10:23:46 1.2 +++ README 2000/08/01 21:18:36 1.3 @@ -2,9 +2,9 @@ Service: ------- -To install this service on a IBM-SOAP listener, you need to make +To install this service on a XML-SOAP listener, you need to make the samples.stockquote.GetQuote class available on the -IBM-SOAP listener's classpath. Then deploy this service by filling +XML-SOAP listener's classpath. Then deploy this service by filling in the deployment template using the info in the deployment descriptor in this directory. @@ -38,7 +38,7 @@ ------------ java samples.stockquote.GetQuote \ - http://localhost:2020/ibm-soap/rpcrouter.jsp IBM + http://localhost:2020/xml-soap/rpcrouter.jsp IBM java samples.stockquote.GetQuoteSMTP \ mailto:carlavasquez@example.net smtpserver.myplace.com \ 1.3 +1 -1 xml-soap/java/src/org/apache/soap/server/ServerConstants.java Index: ServerConstants.java =================================================================== RCS file: /home/cvs/xml-soap/java/src/org/apache/soap/server/ServerConstants.java,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- ServerConstants.java 2000/05/30 10:24:05 1.2 +++ ServerConstants.java 2000/08/01 21:18:37 1.3 @@ -65,7 +65,7 @@ public class ServerConstants { // service name of the service manager public static final String SERVICE_MANAGER_SERVICE_NAME = - "urn:ibm-soap-service-management-service"; + "urn:xml-soap-service-management-service"; // HTTP status codes. public static final int SC_BAD_REQUEST = 400; 1.2 +39 -21 xml-soap/java/webapps/admin/soapadmin.gif <<Binary file>> From carlavasquez@example.net Tue Aug 1 22:29:21 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 35661 invoked from network); 1 Aug 2000 22:29:21 -0000 Received: from d06lmsgate-3.uk.ibm.com (HELO d06lmsgate-3.emea.ibm.com) (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 22:29:21 -0000 Received: from d06relay01.portsmouth.uk.ibm.com (d06relay01.portsmouth.uk.ibm.com [83.161.120.155]) by d06lmsgate-3.emea.ibm.com (1.0.0) with ESMTP id XAA23838 for <carlavasquez@example.net>; Tue, 1 Aug 2000 23:20:39 +0100 Received: from gnkhelp308.greenock.uk.ibm.com (gnkhelp308.greenock.uk.ibm.com [83.161.120.155]) by d06relay01.portsmouth.uk.ibm.com (8.8.8m3/NCO v4.92) with ESMTP id XAA75514 for <carlavasquez@example.net>; Tue, 1 Aug 2000 23:28:34 +0100 Received: from roadkill.rchland.ibm.com (roadkill.rchland.ibm.com [83.161.120.155]) by gnkhelp308.greenock.uk.ibm.com (AIX4.3/UCB 8.8.8/8.8.8) with SMTP id WAA24284 for <carlavasquez@example.net>; Tue, 1 Aug 2000 22:27:18 GMT Message-Id: <carlavasquez@example.net> From: "Wouter Cloetens" <carlavasquez@example.net> To: "carlavasquez@example.net" <carlavasquez@example.net> Date: Tue, 01 Aug 2000 17:27:29 +0600 Reply-To: "Wouter Cloetens" <carlavasquez@example.net> Priority: Normal X-Mailer: PMMail 1.96a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Decoupling of Call X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Thu, 27 Jul 2000 16:51:44 -0500, Steven J. McDowall wrote: >3) The current encapsulation is horrid in that it your are very much >locked into the "invoke" logic with very little (basically none) ability >to change its style.. / methodology, etc. >5) The code changes are DONE fer-gods-sakes.. And tested against all the >demo's and some other hand-rolled stuff.. I'm not sure I agree completely with the implementation of those changes. It's still very much stuck on the RPC paradigm, rather than messaging. For example, you've put everything in Call, even receive(), generating a Response object. I can't map the case where I simply want to listen for a message into that. That's not just an issue with the design of the rpc package; SOAPTransport lacks support too. To clarify... This can be for the existing RPC situation inside rpcrouter. Why would *it* have to build the whole Call object? Why not extend the HTTP transport type (SOAPHTTPConnection, or maybe a new SOAPHTTPServer class) to which the servlet/jsp can pass the request and response objects, or maybe the headers, the InputStream and OutputStream? Or, when using a transport type that allows for a unidirectional message to be sent (mail or messaging middleware) which doesn't necessarily fit either the "Call" or "Response" model (maybe that should be supported by "RPCMessage" or a new "Datagram" class or something). That type of message may not always be received by an HTTP bridge program. The target may just want the message directly - no RPC routing required. The design of SOAPTransport (and therefore Call) assumes that send() will be invoked first, and that will do all the work. receive() is just there to actually get the response if you want it. You can't get it to, for instance, receive a message from a servlet request, a queue, a mail server, a publish/subscribe topic... Fortunately, you did implement a responseFromReader() and responseFromString() which at least takes some of the effort out of it. A JMS implementation of SOAP sounds better every day. :-) Oh just ignore my rant. We'll fix it in a future version. I support your change for the current release. Here's a patch that's identical to your version, with the addition of being able to call send() without a call envelope and/or without headers. bfn, Wouter --- xml-soap/java/src/org/apache/soap/rpc/Call.java.orig Tue May 30 05:24:00 2000 +++ xml-soap/java/src/org/apache/soap/rpc/Call.java Tue Aug 1 17:20:22 2000 @@ -80,82 +80,61 @@ */ public class Call extends RPCMessage { - private XMLParserLiaison xpl = new XercesParserLiaison(); - private SOAPMappingRegistry smr = new SOAPMappingRegistry(); - private SOAPTransport st = new SOAPHTTPConnection(); + private XMLParserLiaison xpl = new XercesParserLiaison (); + private SOAPMappingRegistry smr = new SOAPMappingRegistry (); + private SOAPTransport st = new SOAPHTTPConnection (); - public Call() + public Call () { - this(null, null, null, null, null); + this (null, null, null, null, null); } - public Call(String targetObjectURI, String methodName, Vector params, - Header header, String encodingStyleURI) + public Call (String targetObjectURI, String methodName, Vector params, + Header header, String encodingStyleURI) { - super(targetObjectURI, methodName, params, header, encodingStyleURI); + super (targetObjectURI, methodName, params, header, encodingStyleURI); } - public void setSOAPMappingRegistry(SOAPMappingRegistry smr) + public void setSOAPMappingRegistry (SOAPMappingRegistry smr) { this.smr = smr; } - public SOAPMappingRegistry getSOAPMappingRegistry() + public SOAPMappingRegistry getSOAPMappingRegistry () { return smr; } - public void setSOAPTransport(SOAPTransport st) + public void setSOAPTransport (SOAPTransport st) { this.st = st; } - public SOAPTransport getSOAPTransport() + public SOAPTransport getSOAPTransport () { return st; } - public Envelope buildEnvelope() + public Envelope buildEnvelope () { - return super.buildEnvelope(false); + return super.buildEnvelope (false); } - public static Call extractFromEnvelope(Envelope env, ServiceManager svcMgr) + public static Call extractFromEnvelope (Envelope env, ServiceManager svcMgr) throws IllegalArgumentException { - return (Call)RPCMessage.extractFromEnvelope(env, svcMgr, false, null); + return (Call)RPCMessage.extractFromEnvelope (env, svcMgr, false, null); } /** - * Invoke this call at the specified URL. Valid only on the client side. + * Return the main element (unmarshalled) given the payload */ - public Response invoke(URL url, String SOAPActionURI) throws SOAPException + public Element getElementFromString (String payloadStr) + throws SOAPException { - if (SOAPActionURI == null) - { - SOAPActionURI = ""; - } - - try - { - // Build an envelope containing the call. - Envelope callEnv = buildEnvelope(); - - // Post the call envelope. - st.send(url, SOAPActionURI, null, callEnv, smr); - - // Get the input stream to read the response envelope from. - BufferedReader in = st.receive(); - - /* - Must pre-read the incoming stream to avoid the parser drying up - the stream in case a parsing error occurs. - */ - String payloadStr = IOUtils.getStringFromReader(in); - // Parse the incoming response stream. - Document respDoc = xpl.read("- SOAP HTTP RPC Response Envelope -", - new StringReader(payloadStr)); + Document respDoc = xpl.read ("- SOAP HTTP RPC Response Envelope -", + new StringReader(payloadStr)); Element payload = null; if (respDoc != null) @@ -164,26 +143,152 @@ } else { - throw new SOAPException(Constants.FAULT_CODE_PROTOCOL, - payloadStr); + throw new SOAPException (Constants.FAULT_CODE_PROTOCOL, + payloadStr); } + return payload; + } + + /** + * Parse a response given a streaming reader.. + */ + public String getPayloadFromReader (BufferedReader in) + throws SOAPException + { + /* + Must pre-read the incoming stream to avoid the parser drying up + the stream in case a parsing error occurs. + */ + String payloadStr; + try + { + payloadStr = IOUtils.getStringFromReader (in); + } + catch (IOException e) + { + throw new SOAPException (Constants.FAULT_CODE_PROTOCOL, + e.getMessage (), e); + } + + return payloadStr; + } + + /** + * Parse a response given a streaming reader. + */ + public Response responseFromReader (BufferedReader in) + throws SOAPException + { + /* + Must pre-read the incoming stream to avoid the parser drying up + the stream in case a parsing error occurs. + */ + String payloadStr = getPayloadFromReader (in); + + Response resp = responseFromString (payloadStr); + + return resp; + } + + /** + * Parse a response given a payload string of the whole thing. + */ + public Response responseFromString (String payloadStr) + throws SOAPException + { + // Extract the main body element (which should be the SOAP Envelope) + // from the response payload + Element payload = getElementFromString (payloadStr); + // Unmarshall the response envelope. - Envelope respEnv = Envelope.unmarshall(payload); + Envelope respEnv = Envelope.unmarshall (payload); // Extract the response from the response envelope. - Response resp = Response.extractFromEnvelope(respEnv, smr); + Response resp = Response.extractFromEnvelope (respEnv, smr); + + return resp; + } + + /** + * Create a SOAP request and send it down the pipe. + */ + public void send (URL url, String SOAPActionURI, Hashtable headers, + Envelope callEnv) throws SOAPException + { + if (SOAPActionURI == null) + { + SOAPActionURI = ""; + } + try + { + // Post the call envelope. + st.send (url, SOAPActionURI, headers, callEnv, smr); + } + catch (IllegalArgumentException e) + { + throw new SOAPException(Constants.FAULT_CODE_CLIENT, e.getMessage(), + e); + } + } + + /** + * Build envelope and send message. + */ + public void send (URL url, String SOAPActionURI, Hashtable headers) + throws SOAPException + { + // Build an envelope containing the call. + Envelope callEnv = buildEnvelope(); + + send (url, SOAPActionURI, headers, callEnv); + } + + /** + * Build envelope and send message. This version requires no headers. + */ + public void send (URL url, String SOAPActionURI) + throws SOAPException + { + send (url, SOAPActionURI, null); + } + + /** + * Receive response. + */ + public Response receive() throws SOAPException + { + // Get the input stream to read the response envelope from. + BufferedReader in = st.receive(); + + // Parse the response and send the result back + Response resp = responseFromReader(in); + return resp; + } + + /** + * Invoke this call at the specified URL. Valid only on the client side. + * This version allows the optional headers to be specified. + */ + public Response invoke(URL url, String SOAPActionURI, Hashtable headers) + throws SOAPException + { + // Build an envelope containing the call. + Envelope callEnv = buildEnvelope(); + + send(url, SOAPActionURI, headers, callEnv); + + Response resp = receive(); return resp; - } - catch (IllegalArgumentException e) - { - throw new SOAPException(Constants.FAULT_CODE_CLIENT, e.getMessage(), e); - } - catch (IOException e) - { - throw new SOAPException(Constants.FAULT_CODE_PROTOCOL, - e.getMessage(), e); - } + } + + /** + * Invoke this call at the specified URL. Valid only on the client side. + */ + public Response invoke(URL url, String SOAPActionURI) + throws SOAPException + { + return invoke (url, SOAPActionURI, null); } } From carlavasquez@example.net Tue Aug 1 23:19:35 2000 Return-Path: <carlavasquez@example.net> Mailing-List: contact carlavasquez@example.net; run by ezmlm Delivered-To: mailing list carlavasquez@example.net Received: (qmail 67284 invoked from network); 1 Aug 2000 23:19:35 -0000 Received: from mplspop2.mpls.uswest.net (83.161.120.155) by locus.apache.org with SMTP; 1 Aug 2000 23:19:35 -0000 Received: (qmail 20752 invoked by alias); 1 Aug 2000 23:12:20 -0000 Delivered-To: carlavasquez@example.net@fixme Received: (qmail 11951 invoked by uid 0); 1 Aug 2000 23:06:27 -0000 Received: from pppdsle130.mpls.uswest.net (HELO pooh) (83.161.120.155) by mplspop2.mpls.uswest.net with SMTP; 1 Aug 2000 23:06:27 -0000 Reply-To: <carlavasquez@example.net> From: "Steven J. McDowall" <carlavasquez@example.net> To: <carlavasquez@example.net> Subject: RE: Decoupling of Call Date: Tue, 1 Aug 2000 18:07:04 -0500 Message-ID: <carlavasquez@example.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal In-Reply-To: <carlavasquez@example.net> X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N Wouter, You have a valid point, and your ideas are probably a much better overall plan in general, as well an Sanjiva's idea of some "messaging" abstraction (which seems sort of vague.. ) However, the reason I made the changes and suggested them is because even within the aspect of an RPC situation, there was too little flexibility .. For example, not being able to modify or even submit my own built SOAP envelope to the send() routine, etc. Everything was "automagic" .. So, I figured a little decomposition which allowed flexibility in the short run was a good thing.. I also figured that there wasn't going to be ANY sort of changes that you opined about anytime soon and that flexibility in the short-term was worth more than purity (or hoped for purity) months from now.. :-) So, I agree that my decomposition of Call is hardly the optimal solution we want long term, but it may be more useful than nothing.. -Steve P.S. As for a use case where you may just want to listen? How about having some sort of async. server that, after sending a message, needs to wait on multiple events.. and if the socket gets it (with the response) wants to receive() that message.. -----Original Message----- From: Wouter Cloetens [mailto:carlavasquez@example.net] Sent: Tuesday, August 01, 2000 6:27 AM To: carlavasquez@example.net Subject: Decoupling of Call On Thu, 27 Jul 2000 16:51:44 -0500, Steven J. McDowall wrote: >3) The current encapsulation is horrid in that it your are very much >locked into the "invoke" logic with very little (basically none) ability >to change its style.. / methodology, etc. >5) The code changes are DONE fer-gods-sakes.. And tested against all the >demo's and some other hand-rolled stuff.. I'm not sure I agree completely with the implementation of those changes. It's still very much stuck on the RPC paradigm, rather than messaging. For example, you've put everything in Call, even receive(), generating a Response object. I can't map the case where I simply want to listen for a message into that. That's not just an issue with the design of the rpc package; SOAPTransport lacks support too. To clarify... This can be for the existing RPC situation inside rpcrouter. Why would *it* have to build the whole Call object? Why not extend the HTTP transport type (SOAPHTTPConnection, or maybe a new SOAPHTTPServer class) to which the servlet/jsp can pass the request and response objects, or maybe the headers, the InputStream and OutputStream? Or, when using a transport type that allows for a unidirectional message to be sent (mail or messaging middleware) which doesn't necessarily fit either the "Call" or "Response" model (maybe that should be supported by "RPCMessage" or a new "Datagram" class or something). That type of message may not always be received by an HTTP bridge program. The target may just want the message directly - no RPC routing required. The design of SOAPTransport (and therefore Call) assumes that send() will be invoked first, and that will do all the work. receive() is just there to actually get the response if you want it. You can't get it to, for instance, receive a message from a servlet request, a queue, a mail server, a publish/subscribe topic... Fortunately, you did implement a responseFromReader() and responseFromString() which at least takes some of the effort out of it. A JMS implementation of SOAP sounds better every day. :-) Oh just ignore my rant. We'll fix it in a future version. I support your change for the current release. Here's a patch that's identical to your version, with the addition of being able to call send() without a call envelope and/or without headers. bfn, Wouter --- xml-soap/java/src/org/apache/soap/rpc/Call.java.orig Tue May 30 05:24:00 2000 +++ xml-soap/java/src/org/apache/soap/rpc/Call.java Tue Aug 1 17:20:22 2000 @@ -80,82 +80,61 @@ */ public class Call extends RPCMessage { - private XMLParserLiaison xpl = new XercesParserLiaison(); - private SOAPMappingRegistry smr = new SOAPMappingRegistry(); - private SOAPTransport st = new SOAPHTTPConnection(); + private XMLParserLiaison xpl = new XercesParserLiaison (); + private SOAPMappingRegistry smr = new SOAPMappingRegistry (); + private SOAPTransport st = new SOAPHTTPConnection (); - public Call() + public Call () { - this(null, null, null, null, null); + this (null, null, null, null, null); } - public Call(String targetObjectURI, String methodName, Vector params, - Header header, String encodingStyleURI) + public Call (String targetObjectURI, String methodName, Vector params, + Header header, String encodingStyleURI) { - super(targetObjectURI, methodName, params, header, encodingStyleURI); + super (targetObjectURI, methodName, params, header, encodingStyleURI); } - public void setSOAPMappingRegistry(SOAPMappingRegistry smr) + public void setSOAPMappingRegistry (SOAPMappingRegistry smr) { this.smr = smr; } - public SOAPMappingRegistry getSOAPMappingRegistry() + public SOAPMappingRegistry getSOAPMappingRegistry () { return smr; } - public void setSOAPTransport(SOAPTransport st) + public void setSOAPTransport (SOAPTransport st) { this.st = st; } - public SOAPTransport getSOAPTransport() + public SOAPTransport getSOAPTransport () { return st; } - public Envelope buildEnvelope() + public Envelope buildEnvelope () { - return super.buildEnvelope(false); + return super.buildEnvelope (false); } - public static Call extractFromEnvelope(Envelope env, ServiceManager svcMgr) + public static Call extractFromEnvelope (Envelope env, ServiceManager svcMgr) throws IllegalArgumentException { - return (Call)RPCMessage.extractFromEnvelope(env, svcMgr, false, null); + return (Call)RPCMessage.extractFromEnvelope (env, svcMgr, false, null); } /** - * Invoke this call at the specified URL. Valid only on the client side. + * Return the main element (unmarshalled) given the payload */ - public Response invoke(URL url, String SOAPActionURI) throws SOAPException + public Element getElementFromString (String payloadStr) + throws SOAPException { - if (SOAPActionURI == null) - { - SOAPActionURI = ""; - } - - try - { - // Build an envelope containing the call. - Envelope callEnv = buildEnvelope(); - - // Post the call envelope. - st.send(url, SOAPActionURI, null, callEnv, smr); - - // Get the input stream to read the response envelope from. - BufferedReader in = st.receive(); - - /* - Must pre-read the incoming stream to avoid the parser drying up - the stream in case a parsing error occurs. - */ - String payloadStr = IOUtils.getStringFromReader(in); - // Parse the incoming response stream. - Document respDoc = xpl.read("- SOAP HTTP RPC Response Envelope -", - new StringReader(payloadStr)); + Document respDoc = xpl.read ("- SOAP HTTP RPC Response Envelope -", + new StringReader(payloadStr)); Element payload = null; if (respDoc != null) @@ -164,26 +143,152 @@ } else { - throw new SOAPException(Constants.FAULT_CODE_PROTOCOL, - payloadStr); + throw new SOAPException (Constants.FAULT_CODE_PROTOCOL, + payloadStr); } + return payload; + } + + /** + * Parse a response given a streaming reader.. + */ + public String getPayloadFromReader (BufferedReader in) + throws SOAPException + { + /* + Must pre-read the incoming stream to avoid the parser drying up + the stream in case a parsing error occurs. + */ + String payloadStr; + try + { + payloadStr = IOUtils.getStringFromReader (in); + } + catch (IOException e) + { + throw new SOAPException (Constants.FAULT_CODE_PROTOCOL, + e.getMessage (), e); + } + + return payloadStr; + } + + /** + * Parse a response given a streaming reader. + */ + public Response responseFromReader (BufferedReader in) + throws SOAPException + { + /* + Must pre-read the incoming stream to avoid the parser drying up + the stream in case a parsing error occurs. + */ + String payloadStr = getPayloadFromReader (in); + + Response resp = responseFromString (payloadStr); + + return resp; + } + + /** + * Parse a response given a payload string of the whole thing. + */ + public Response responseFromString (String payloadStr) + throws SOAPException + { + // Extract the main body element (which should be the SOAP Envelope) + // from the response payload + Element payload = getElementFromString (payloadStr); + // Unmarshall the response envelope. - Envelope respEnv = Envelope.unmarshall(payload); + Envelope respEnv = Envelope.unmarshall (payload); // Extract the response from the response envelope. - Response resp = Response.extractFromEnvelope(respEnv, smr); + Response resp = Response.extractFromEnvelope (respEnv, smr); + + return resp; + } + + /** + * Create a SOAP request and send it down the pipe. + */ + public void send (URL url, String SOAPActionURI, Hashtable headers, + Envelope callEnv) throws SOAPException + { + if (SOAPActionURI == null) + { + SOAPActionURI = ""; + } + try + { + // Post the call envelope. + st.send (url, SOAPActionURI, headers, callEnv, smr); + } + catch (IllegalArgumentException e) + { + throw new SOAPException(Constants.FAULT_CODE_CLIENT, e.getMessage(), + e); + } + } + + /** + * Build envelope and send message. + */ + public void send (URL url, String SOAPActionURI, Hashtable headers) + throws SOAPException + { + // Build an envelope containing the call. + Envelope callEnv = buildEnvelope(); + + send (url, SOAPActionURI, headers, callEnv); + } + + /** + * Build envelope and send message. This version requires no headers. + */ + public void send (URL url, String SOAPActionURI) + throws SOAPException + { + send (url, SOAPActionURI, null); + } + + /** + * Receive response. + */ + public Response receive() throws SOAPException + { + // Get the input stream to read the response envelope from. + BufferedReader in = st.receive(); + + // Parse the response and send the result back + Response resp = responseFromReader(in); + return resp; + } + + /** + * Invoke this call at the specified URL. Valid only on the client side. + * This version allows the optional headers to be specified.
{'source': 'Apache Software Foundation Public Mail Archives'}