cvs commit: xml-soap/java/docs/guide rpc.html

2002-06-24 Thread snichol
snichol 2002/06/24 22:29:20 Modified:java/docs/guide rpc.html Log: Add a paragraph about the new service configuration capability to the docs. Revision ChangesPath 1.4 +9 -2 xml-soap/java/docs/guide/rpc.html Index: rpc.html =

Re: TODO list item

2002-06-24 Thread Scott Nichol
Mike, The e-mail below was the commit for the TODO list stuff. There is even a (trivial) sample. Thanks for the contribution. Scott Nichol - Original Message - From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 25, 2002 1:16 AM Subject: cvs commit: xml-soap/java/src

cvs commit: xml-soap/java/src/org/apache/soap/server/http ServerHTTPUtils.java

2002-06-24 Thread snichol
snichol 2002/06/24 22:16:27 Modified:.TODO java/docs changes.html java/docs/guide rpc.html java/docs/install tomcat.html java/src/org/apache/soap/server/http ServerHTTPUtils.java Added: java/samples/configure Co

cvs commit: xml-soap/java/samples/configure - New directory

2002-06-24 Thread snichol
snichol 2002/06/24 22:06:53 xml-soap/java/samples/configure - New directory -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: SOAP app question

2002-06-24 Thread Scott Nichol
I consider the classpath issues to be problems related to Java and servlet container implementations, not Apache SOAP. The class loader requirements in more recent servlet specs have greatly improved things. You do not need to copy soap.jar anywhere. Step 1 under Apache SOAP Client (http://www.

Java Equivalent Code for XSP

2002-06-24 Thread deepak venugopal
hi friends, my previous message was as listed below. The thing is in my Java soap clients i have modified the CALL Objects encoding style with : call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML); and have successfully obtained the return ELEMENT from my Java Soap Service.( I had mentioned t

Re: TODO list item

2002-06-24 Thread Scott Nichol
Not there yet, but it *will* be. Scott - Original Message - From: "Michael Jennings" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 24, 2002 5:01 PM Subject: Re: TODO list item > So it's there? Cool! > -Mike > > - Original Message - > From: "Scott Nichol" <[EMAI

Re: TODO list item

2002-06-24 Thread Michael Jennings
So it's there? Cool! -Mike - Original Message - From: "Scott Nichol" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, June 24, 2002 1:53 PM Subject: Re: TODO list item > Yes, in modified form with the additional properties sources (e.g. > deployment descriptor). > > Scott > > -

Re: TODO list item

2002-06-24 Thread Scott Nichol
Yes, in modified form with the additional properties sources (e.g. deployment descriptor). Scott - Original Message - From: "Michael Jennings" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, June 22, 2002 1:11 PM Subject: Re: TODO list item > Hi Scott, > > Any chance of tha

Re: SOAP app question

2002-06-24 Thread Scott Nichol
With Tomcat 4.x, you do not need to make any changes to the classpath or startup scripts for Tomcat. You merely deploy Apache SOAP as a Web application. See, for example, http://www.scottnichol.com/apachesoapinstall.htm. Scott Nichol - Original Message - From: "FitMe Marketing" <[EMAIL

SOAP app question

2002-06-24 Thread FitMe Marketing
Hi: We recently downloaded Tomcat 4.0.4 and SOAP 2.3 on a Win2K server. We modified the catalina.bat file to reflect the fact that we needed a JAXP compatible XML parser first in the classpath. *** set CLASSPATH=%CLASSPATH%;%CATALINA_HOME%\bin\bootstrap.jar set CLASSPATH=path-to-xerces/%CATALINA

Re: Serialization problem!!

2002-06-24 Thread Scott Nichol
Your issue sounds germaine to XML, not SOAP. Be certain to try post your question to the relevant list. Scott - Original Message - From: "Jeong Ahn Lee" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, June 24, 2002 2:50 AM Subject: Serialization problem!!

Re: Serialization problem!!

2002-06-24 Thread Scott Nichol
Actually, if your error really is "no serializer found for org.w3c.node", then this means the server cannot find a serializer, which very likely means your Java clients use literal XML encoding. Scott Nichol - Original Message - From: "Scott Nichol" <[EMAIL PROTECTED]> To: <[EMAIL PROTEC

Re: Serialization problem!!

2002-06-24 Thread Scott Nichol
Please check your Java clients that handle a return Element. I suspect they either use literal XML encoding (not SOAP encoding) or they add a deserializer for Element to the mapping registry. Your XSP code must, of course, do the same in order to work. Scott Nichol - Original Message -

How to Write XSP Code - equivalent to Java Soap Clients

2002-06-24 Thread deepak venugopal
Hello friends, My company has started developing soap clients based on XSP and submitting the request to Apache Soap Server which has services running in pure Java. For my Java Soap Clients, the soap service used to return a Node Element ( XML Document). The Java Client worked perfectly using the

Re: Serialization problem!!

2002-06-24 Thread deepak venugopal
Hello friends, My company has started developing soap clients based on XSP and submitting the request to Apache Soap Server which has services running in pure Java. For my Java Soap Clients, the soap service used to return a Node Element ( XML Document). The Java Client worked perfectly using the