Re: SAXParser ?

Your results agree with mine: the transform is slower than the document builder. Maybe it's just the Xalan/Xerces implementation, as I used those as well. The problem with not using reflection is that it is hard to predict where the NoClassDefFoundError exceptions will be thrown. The JVM spec a

improving client performance tricks

Hi, In discussion over performance improvements I also propose share tricks which could be used in own code, without touching SOAP (or other ) libs. Often it gives more result, that asking to improve other's code. And only once you are sure that you used everything... So, we had a client side app

Re: SAXParser ?

Actually, I may be incorrect to say that users would have to upgrade their XML parser. It is possible that something like Xalan would work with their existing parser, but then Xalan (or similar) would become a dependency for Apache SOAP. Scott Nichol - Original Message - From: "Scott Nic

RE: SAXParser ?

Scott, I'm not going to discuss the perfomance changes by switching to SAX parsing with producing DOMResult - just don't know if it could be, but I'm interesting what is the primary reason for using reflection API and Class.forName, instead of using classes directly - this actually could be perfo

FW: soap_closesock()??

Hi guys. I'm trying to close all the soap sockets, that did a SOAP call but I don't know how. I'm working with Axis API (JAVA). Thanks Marios -- To unsubscribe, e-mail: For additional commands, e-mail:

Re: SAXParser ?

In short, I would love to have a speedier, SAX-based Apache SOAP, but I don't know where the effort would come from to do the work. I don't know of any time that any developer(s) said Apache SOAP would be moving to using SAX, and I know of no plans to do so. A significant part of very early Axis

RE: SAXParser ?

Scott, Sorry, I don't understand how could we force user to upgrade their xerces. On the runtime, your code will not work with xerces 1.x anyway, if the classes not available. However once we compiled soap library with having xalan / cerses 2 in classpath we should be able to run soap lib without

Re: soap_closesock()??

You may want to look at org.apache.axis.transport.http.HTTPSender#invoke. It uses a local variable "sock" for the socket created by getSocket, calls writeToSocket and readFromSocket, then exits the scope in which sock is declared. If this invoke method is how RPC calls are made, then you don't ha

Re: SAXParser ?

I decided to put together a standalone test of the 2 parsing methods. The results I get from a file containing a SOAP envelope for a response message with a return value array of 1 string elements is DocumentBuilder: 809 Transform: 1243 where the number is milliseconds to parse. I will make

Re: SAXParser ?

My test can be downloaded at http://www.scottnichol.com/XMLParseTest.zip. Scott Nichol - Original Message - From: "Scott Nichol" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, October 17, 2002 2:27 PM Subject: Re: SAXParser ? > I decided to put together a standalone test of

Re: SAXParser ?

If reflection were not used, we would have a dependency on a later version of JAXP, which would require many users to upgrade their XML parser. In particular, most users seem to use Xerces 1.x. The only JAXP classes provided by it are javax/xml/parsers/DocumentBuilder.class javax/xml/par

[PATCH] Allow client to set up set transport headers

Hello, Here is a patch to enable clients to set up transport headers for sending envelope. Patched files are Call & Message, additional methods added with support to headers param Best regards, Pavel Index: Message.java === RCS fil

Question!!!

Hi, A question for all. I want to develop a client which sends a SOAP Request and get back a Response. For the SOAP Response parsing, I'll use a normal non-validating XML Parser. I am not worried about validation using XML Schema and XML Namespace in the Response. While sending a Request I 'll send

[PATCH] Allow to disable "CleanString" usage for clients

Hello, We have a problem with our client application, when a SOAP exception occurs, because of server error (like it returns 500 or other error, with HTML instead of XML. When we log the exception to the file, the text is unreadable see below Unsupported response content type "text/html; charset=

Re: Question!!!

Schema validation in Web services remains rare. In .NET, for example, one cannot enable validation by simply setting an attribute or making a method call, which means that virtually no one using .NET is validating. I don't know how many Apache SOAP users enable validation, but I don't think it is

Re: [PATCH] Allow client to set up set transport headers

This is great. I will apply in a few moments. Scott Nichol - Original Message - From: "Pavel Ausianik" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, October 18, 2002 8:02 AM Subject: [PATCH] Allow client to set up set transport headers > Hello, > > Here is a patch to enable

Re: [PATCH] Allow to disable "CleanString" usage for clients

I like the intention of this. I think we are all sick of reading these error messages. However, I think there may be a better way to deal with this. The fact is, cleanString has no business being used in SOAPException at all. The only reason cleanString ever needs to be called is that the infor

cvs commit: xml-soap/java/src/org/apache/soap/messaging Message.java

snichol 2002/10/18 06:36:00 Modified:java/docs changes.html java/src/org/apache/soap/rpc Call.java java/src/org/apache/soap/messaging Message.java Log: Submitted by: Pavel Ausianik <[EMAIL PROTECTED]> Here is a patch to enable clients to set up tran

RE: [PATCH] Allow to disable "CleanString" usage for clients

Scott, I agree the way you propose is better one. I just didn't felt strong enough to patch all places were it could make incompatibility to existing services. Thanks, Pavel > -Original Message- > From: Scott Nichol [mailto:snicholnews@;scottnichol.com] > Sent: Friday, October 18, 2002 4

Re: [PATCH] Allow to disable "CleanString" usage for clients

With something used everywhere like SOAPException, I'm worried that I would be breaking something by changing it, but I think the "cleaned" exception messages are so annoying it's worth giving it a try. Scott Nichol - Original Message - From: "Pavel Ausianik" <[EMAIL PROTECTED]> To: <[EMA

cvs commit: xml-soap/java/src/org/apache/soap Fault.java SOAPException.java

snichol 2002/10/18 06:52:30 Modified:java/src/org/apache/soap Fault.java SOAPException.java Log: SOAPException does not need to use cleanString. Removed its use there and added it to marshalling for Fault, where it is needed. Thanks to Pavel Ausianik for getting me to think abo

RE: committing some perf improvements

Hello, it seems like nobody complains, but some looking forward to try ... Thanks, Pavel > -Original Message- > From: Scott Nichol [mailto:snicholnews@;scottnichol.com] > Sent: Wednesday, October 09, 2002 7:08 PM > To: [EMAIL PROTECTED] > Subject: Re: committing some perf improvements >

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

snichol 2002/10/18 08:49:13 Modified:java/docs/guide serializer.html Log: Add a code example of mapping types on the client. Revision ChangesPath 1.7 +40 -7 xml-soap/java/docs/guide/serializer.html Index: serializer.html ==

Re: improving client performance tricks

> Our first design was simple - when you need to make a call, just create > a new one. However creation of a Call is not so light - further it will > also require to create additional DocumentBuilder, and > SOAPMappingRegistry, both not so light. I agree with this point. Some time ago, we switche

cvs commit: xml-soap/java/src/org/apache/soap/util/net HTTPUtils.java SSLUtils.java

snichol 2002/10/18 13:30:54 Modified:java/src/org/apache/soap/util/net HTTPUtils.java SSLUtils.java Log: Allow proxyUserName and proxyPassword to be used for SSL connection as well as straight HTTP. Move all auth string manipulation out of SSLUtils. Th

cvs commit: xml-soap/java/src/org/apache/soap SOAPException.java

snichol 2002/10/18 13:27:18 Modified:java/src/org/apache/soap SOAPException.java Log: Override printStackTrace methods so that the trace for the targetException is also printed automatically. Revision ChangesPath 1.6 +39 -1 xml-soap/java/src/org/apache/soap/SO