You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by "William A. Nagy" <na...@watson.ibm.com> on 2002/05/13 22:05:50 UTC
Vote: Apache SOAP 2.3 Release Schedule
I'd like to call for a vote on the Apache SOAP 2.3 Release Plan.
The vote will run until 04/25.
<ballot>
[ ] +1 I approve this plan, and will help
[ ] +0 I approve this plan, but can't help
[ ] -0 I am not in favor of this plan
[ ] -1 I am against this plan, because:
</ballot>
-Bill
Release Plan for Apache SOAP 2.3
==================================
Introduction:
------------
This document is a release plan for the release of Apache SOAP
2.3.
The goal of the Apache SOAP 2.3 release is to capture all of the
bug-fixes that have been made since v2.2 in a "permanent" build.
This Release Plan proposes the following schedule:
Wednesday, May 15, 2002 Apache SOAP 2.3 Beta 1
Wednesday, May 22, 2002 Apache SOAP 2.3 Release Candidate
Friday, May 24, 2002 Apache SOAP 2.3 Release
This is an aggressive schedule, but no significant functionality has
been added since 2.2 and most people are already using the nightly
builds.
After the first 2.3 Release Candidate, other RC releases may be made
as needed until one is promoted as Final by the SOAP committers.
If you discover any outstanding bugs, please post them to Bugzilla.
Re: Apache SOAP 2.3 Release Schedule
Posted by "William A. Nagy" <na...@watson.ibm.com>.
We don't tag (or branch) the code until we do an actual release.
You're pretty safe with just doing a cvs checkout (we haven't made a
lot of modifications since the rc went up.) If you want the exact
code, you can checkout the code from the exact day that we put the rc
up.
-Bill
Re: Apache SOAP 2.3 Release Schedule
Posted by "William A. Nagy" <na...@watson.ibm.com>.
We don't tag (or branch) the code until we do an actual release.
You're pretty safe with just doing a cvs checkout (we haven't made a
lot of modifications since the rc went up.) If you want the exact
code, you can checkout the code from the exact day that we put the rc
up.
-Bill
Re: Apache SOAP 2.3 Release Schedule
Posted by Dan Davis <da...@caip.rutgers.edu>.
How can I retrieve the release candidate from CVS? Is there a branch
I can use or did I get the release candidate just be doing a cvs checkout
or update with no arguments?
Re: Apache SOAP 2.3 Release Schedule
Posted by Dan Davis <da...@caip.rutgers.edu>.
How can I retrieve the release candidate from CVS? Is there a branch
I can use or did I get the release candidate just be doing a cvs checkout
or update with no arguments?
Re: Apache SOAP 2.3 Release Schedule
Posted by Paco Avila <fa...@gridsystems.com>.
<ballot>
+0
</ballot>
----- Original Message -----
From: "William A. Nagy" <na...@watson.ibm.com>
To: <so...@xml.apache.org>
Sent: Monday, May 13, 2002 10:05 PM
Subject: Vote: Apache SOAP 2.3 Release Schedule
> I'd like to call for a vote on the Apache SOAP 2.3 Release Plan.
>
> The vote will run until 04/25.
>
> <ballot>
> [ ] +1 I approve this plan, and will help
> [ ] +0 I approve this plan, but can't help
> [ ] -0 I am not in favor of this plan
> [ ] -1 I am against this plan, because:
>
> </ballot>
>
> -Bill
>
>
> Release Plan for Apache SOAP 2.3
> ==================================
>
> Introduction:
> ------------
>
> This document is a release plan for the release of Apache SOAP
> 2.3.
>
> The goal of the Apache SOAP 2.3 release is to capture all of the
> bug-fixes that have been made since v2.2 in a "permanent" build.
>
> This Release Plan proposes the following schedule:
>
> Wednesday, May 15, 2002 Apache SOAP 2.3 Beta 1
>
> Wednesday, May 22, 2002 Apache SOAP 2.3 Release Candidate
>
> Friday, May 24, 2002 Apache SOAP 2.3 Release
>
> This is an aggressive schedule, but no significant functionality has
> been added since 2.2 and most people are already using the nightly
> builds.
>
> After the first 2.3 Release Candidate, other RC releases may be made
> as needed until one is promoted as Final by the SOAP committers.
>
> If you discover any outstanding bugs, please post them to Bugzilla.
>
>
>
>
>
Re: Apache SOAP 2.3 Release Schedule
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
+1.
----- Original Message -----
From: "William A. Nagy" <na...@watson.ibm.com>
To: <so...@xml.apache.org>
Sent: Tuesday, May 14, 2002 2:05 AM
Subject: Vote: Apache SOAP 2.3 Release Schedule
> I'd like to call for a vote on the Apache SOAP 2.3 Release Plan.
>
> The vote will run until 04/25.
>
> <ballot>
> [ ] +1 I approve this plan, and will help
> [ ] +0 I approve this plan, but can't help
> [ ] -0 I am not in favor of this plan
> [ ] -1 I am against this plan, because:
>
> </ballot>
>
> -Bill
>
>
> Release Plan for Apache SOAP 2.3
> ==================================
>
> Introduction:
> ------------
>
> This document is a release plan for the release of Apache SOAP
> 2.3.
>
> The goal of the Apache SOAP 2.3 release is to capture all of the
> bug-fixes that have been made since v2.2 in a "permanent" build.
>
> This Release Plan proposes the following schedule:
>
> Wednesday, May 15, 2002 Apache SOAP 2.3 Beta 1
>
> Wednesday, May 22, 2002 Apache SOAP 2.3 Release Candidate
>
> Friday, May 24, 2002 Apache SOAP 2.3 Release
>
> This is an aggressive schedule, but no significant functionality has
> been added since 2.2 and most people are already using the nightly
> builds.
>
> After the first 2.3 Release Candidate, other RC releases may be made
> as needed until one is promoted as Final by the SOAP committers.
>
> If you discover any outstanding bugs, please post them to Bugzilla.
>
>
>
Re: Apache SOAP 2.3 Release Schedule
Posted by Paco Avila <fa...@gridsystems.com>.
<ballot>
+0
</ballot>
----- Original Message -----
From: "William A. Nagy" <na...@watson.ibm.com>
To: <so...@xml.apache.org>
Sent: Monday, May 13, 2002 10:05 PM
Subject: Vote: Apache SOAP 2.3 Release Schedule
> I'd like to call for a vote on the Apache SOAP 2.3 Release Plan.
>
> The vote will run until 04/25.
>
> <ballot>
> [ ] +1 I approve this plan, and will help
> [ ] +0 I approve this plan, but can't help
> [ ] -0 I am not in favor of this plan
> [ ] -1 I am against this plan, because:
>
> </ballot>
>
> -Bill
>
>
> Release Plan for Apache SOAP 2.3
> ==================================
>
> Introduction:
> ------------
>
> This document is a release plan for the release of Apache SOAP
> 2.3.
>
> The goal of the Apache SOAP 2.3 release is to capture all of the
> bug-fixes that have been made since v2.2 in a "permanent" build.
>
> This Release Plan proposes the following schedule:
>
> Wednesday, May 15, 2002 Apache SOAP 2.3 Beta 1
>
> Wednesday, May 22, 2002 Apache SOAP 2.3 Release Candidate
>
> Friday, May 24, 2002 Apache SOAP 2.3 Release
>
> This is an aggressive schedule, but no significant functionality has
> been added since 2.2 and most people are already using the nightly
> builds.
>
> After the first 2.3 Release Candidate, other RC releases may be made
> as needed until one is promoted as Final by the SOAP committers.
>
> If you discover any outstanding bugs, please post them to Bugzilla.
>
>
>
>
>
Re: Apache SOAP 2.3 Release Schedule
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
+1.
----- Original Message -----
From: "William A. Nagy" <na...@watson.ibm.com>
To: <so...@xml.apache.org>
Sent: Tuesday, May 14, 2002 2:05 AM
Subject: Vote: Apache SOAP 2.3 Release Schedule
> I'd like to call for a vote on the Apache SOAP 2.3 Release Plan.
>
> The vote will run until 04/25.
>
> <ballot>
> [ ] +1 I approve this plan, and will help
> [ ] +0 I approve this plan, but can't help
> [ ] -0 I am not in favor of this plan
> [ ] -1 I am against this plan, because:
>
> </ballot>
>
> -Bill
>
>
> Release Plan for Apache SOAP 2.3
> ==================================
>
> Introduction:
> ------------
>
> This document is a release plan for the release of Apache SOAP
> 2.3.
>
> The goal of the Apache SOAP 2.3 release is to capture all of the
> bug-fixes that have been made since v2.2 in a "permanent" build.
>
> This Release Plan proposes the following schedule:
>
> Wednesday, May 15, 2002 Apache SOAP 2.3 Beta 1
>
> Wednesday, May 22, 2002 Apache SOAP 2.3 Release Candidate
>
> Friday, May 24, 2002 Apache SOAP 2.3 Release
>
> This is an aggressive schedule, but no significant functionality has
> been added since 2.2 and most people are already using the nightly
> builds.
>
> After the first 2.3 Release Candidate, other RC releases may be made
> as needed until one is promoted as Final by the SOAP committers.
>
> If you discover any outstanding bugs, please post them to Bugzilla.
>
>
>
RE: Vote: Apache SOAP 2.3 Release Schedule
Posted by "Matthew J. Duftler" <du...@watson.ibm.com>.
<ballot>
[X] +1 I approve this plan, and will help
[ ] +0 I approve this plan, but can't help
[ ] -0 I am not in favor of this plan
[ ] -1 I am against this plan, because:
</ballot>
> -----Original Message-----
> From: William A. Nagy [mailto:nagy@watson.ibm.com]
> Sent: Monday, May 13, 2002 4:06 PM
> To: soap-dev@xml.apache.org
> Subject: Vote: Apache SOAP 2.3 Release Schedule
>
>
> I'd like to call for a vote on the Apache SOAP 2.3 Release Plan.
>
> The vote will run until 04/25.
>
> <ballot>
> [ ] +1 I approve this plan, and will help
> [ ] +0 I approve this plan, but can't help
> [ ] -0 I am not in favor of this plan
> [ ] -1 I am against this plan, because:
>
> </ballot>
>
> -Bill
>
>
> Release Plan for Apache SOAP 2.3
> ==================================
>
> Introduction:
> ------------
>
> This document is a release plan for the release of Apache SOAP
> 2.3.
>
> The goal of the Apache SOAP 2.3 release is to capture all of the
> bug-fixes that have been made since v2.2 in a "permanent" build.
>
> This Release Plan proposes the following schedule:
>
> Wednesday, May 15, 2002 Apache SOAP 2.3 Beta 1
>
> Wednesday, May 22, 2002 Apache SOAP 2.3 Release Candidate
>
> Friday, May 24, 2002 Apache SOAP 2.3 Release
>
> This is an aggressive schedule, but no significant functionality has
> been added since 2.2 and most people are already using the nightly
> builds.
>
> After the first 2.3 Release Candidate, other RC releases may be made
> as needed until one is promoted as Final by the SOAP committers.
>
> If you discover any outstanding bugs, please post them to Bugzilla.
>
>
>
>
Re: Changes to Apache SOAP 2.2
Posted by "William A. Nagy" <na...@watson.ibm.com>.
>My Name is Raj . I work for Insurance Company in Scottsdale. Recently
>my company asked me to look into web services. I started downloading
>SOAP stuff from apache site, I wrote small programs every thing works
>great. But when I really started doing prototype of an existing application
>, it doesn't seem to be working right. Like if Data over the wire from
>Database to Tomcat/SOAP server to Browser is minimal then it
>takes few seconds to process, but if data is huge (> 300 Kb) then it really
>slows down. Then I started digging into your code, I found couple of
>things I can change like you guys are using DOM Parser which is Memory
>intensive , So started changing your code to use SAXParser and also I need
>to changing couple of things in your DOMUtils code too. So now it works
>very fast like in seconds I can see output. So I would like share my
>code and see what you guys think , also wants to contribute to
>development. Not sure how to proceed can some body help me on this...
Hi Raj,
As Scott pointed out, Apache SOAP is really in maintenance mode now
and what you are proposing are major changes. I would suggest that
you take a look at Apache Axis and see if they have what you need.
-Bill
Re: Changes to Apache SOAP 2.2
Posted by "William A. Nagy" <na...@watson.ibm.com>.
>My Name is Raj . I work for Insurance Company in Scottsdale. Recently
>my company asked me to look into web services. I started downloading
>SOAP stuff from apache site, I wrote small programs every thing works
>great. But when I really started doing prototype of an existing application
>, it doesn't seem to be working right. Like if Data over the wire from
>Database to Tomcat/SOAP server to Browser is minimal then it
>takes few seconds to process, but if data is huge (> 300 Kb) then it really
>slows down. Then I started digging into your code, I found couple of
>things I can change like you guys are using DOM Parser which is Memory
>intensive , So started changing your code to use SAXParser and also I need
>to changing couple of things in your DOMUtils code too. So now it works
>very fast like in seconds I can see output. So I would like share my
>code and see what you guys think , also wants to contribute to
>development. Not sure how to proceed can some body help me on this...
Hi Raj,
As Scott pointed out, Apache SOAP is really in maintenance mode now
and what you are proposing are major changes. I would suggest that
you take a look at Apache Axis and see if they have what you need.
-Bill
Re: Changes to Apache SOAP 2.2
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Hi Raj,
I would be very interested in seeing this patch. Would you be able
to post it against the latest tree?
While Apache SOAP is basically in maintainence mode, there are still
lots of people using it. If there's a SAX patch that works well
and makes things much faster I'm all ears.
However, it is too late to include it into Apache SOAP 2.3.
Sanjiva.
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Friday, May 24, 2002 1:44 AM
Subject: Re: Changes to Apache SOAP 2.2
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in Scottsdale. Recently
> my company asked me to look into web services. I started downloading
> SOAP stuff from apache site, I wrote small programs every thing works
> great. But when I really started doing prototype of an existing
application
> , it doesn't seem to be working right. Like if Data over the wire from
> Database to Tomcat/SOAP server to Browser is minimal then it
> takes few seconds to process, but if data is huge (> 300 Kb) then it
really
> slows down. Then I started digging into your code, I found couple of
> things I can change like you guys are using DOM Parser which is Memory
> intensive , So started changing your code to use SAXParser and also I need
> to changing couple of things in your DOMUtils code too. So now it works
> very fast like in seconds I can see output. So I would like share my
> code and see what you guys think , also wants to contribute to
> development. Not sure how to proceed can some body help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
Re: Changes to Apache SOAP 2.2
Posted by Scott Nichol <sn...@scottnichol.com>.
Raj,
Pretty much all Apache SOAP development has moved to the Apache Axis project.
That is the next generation code base which will be the reference implementation
of JAX-RPC. It supports WSDL and is SAX-based.
The Apache SOAP committers have discussed releasing the current code as version
2.3, and the first release candidate has been packaged. Your changes sound "too
big" to put into 2.3.
Note, however, that I am not a committer, and it may very well be that the
developers do want your contribution ASAP. If you want to submit your patches,
http://xml.apache.org/source.html tells how to do this.
Scott Nichol
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Thursday, May 23, 2002 3:44 PM
Subject: Re: Changes to Apache SOAP 2.2
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in Scottsdale. Recently
> my company asked me to look into web services. I started downloading
> SOAP stuff from apache site, I wrote small programs every thing works
> great. But when I really started doing prototype of an existing application
> , it doesn't seem to be working right. Like if Data over the wire from
> Database to Tomcat/SOAP server to Browser is minimal then it
> takes few seconds to process, but if data is huge (> 300 Kb) then it really
> slows down. Then I started digging into your code, I found couple of
> things I can change like you guys are using DOM Parser which is Memory
> intensive , So started changing your code to use SAXParser and also I need
> to changing couple of things in your DOMUtils code too. So now it works
> very fast like in seconds I can see output. So I would like share my
> code and see what you guys think , also wants to contribute to
> development. Not sure how to proceed can some body help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
Re: Changes to Apache SOAP 2.2
Posted by Scott Nichol <sn...@scottnichol.com>.
Raj,
Pretty much all Apache SOAP development has moved to the Apache Axis project.
That is the next generation code base which will be the reference implementation
of JAX-RPC. It supports WSDL and is SAX-based.
The Apache SOAP committers have discussed releasing the current code as version
2.3, and the first release candidate has been packaged. Your changes sound "too
big" to put into 2.3.
Note, however, that I am not a committer, and it may very well be that the
developers do want your contribution ASAP. If you want to submit your patches,
http://xml.apache.org/source.html tells how to do this.
Scott Nichol
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Thursday, May 23, 2002 3:44 PM
Subject: Re: Changes to Apache SOAP 2.2
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in Scottsdale. Recently
> my company asked me to look into web services. I started downloading
> SOAP stuff from apache site, I wrote small programs every thing works
> great. But when I really started doing prototype of an existing application
> , it doesn't seem to be working right. Like if Data over the wire from
> Database to Tomcat/SOAP server to Browser is minimal then it
> takes few seconds to process, but if data is huge (> 300 Kb) then it really
> slows down. Then I started digging into your code, I found couple of
> things I can change like you guys are using DOM Parser which is Memory
> intensive , So started changing your code to use SAXParser and also I need
> to changing couple of things in your DOMUtils code too. So now it works
> very fast like in seconds I can see output. So I would like share my
> code and see what you guys think , also wants to contribute to
> development. Not sure how to proceed can some body help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
Re: Changes to Apache SOAP 2.2
Posted by Sanjiva Weerawarana <sa...@watson.ibm.com>.
Hi Raj,
I would be very interested in seeing this patch. Would you be able
to post it against the latest tree?
While Apache SOAP is basically in maintainence mode, there are still
lots of people using it. If there's a SAX patch that works well
and makes things much faster I'm all ears.
However, it is too late to include it into Apache SOAP 2.3.
Sanjiva.
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Friday, May 24, 2002 1:44 AM
Subject: Re: Changes to Apache SOAP 2.2
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in Scottsdale. Recently
> my company asked me to look into web services. I started downloading
> SOAP stuff from apache site, I wrote small programs every thing works
> great. But when I really started doing prototype of an existing
application
> , it doesn't seem to be working right. Like if Data over the wire from
> Database to Tomcat/SOAP server to Browser is minimal then it
> takes few seconds to process, but if data is huge (> 300 Kb) then it
really
> slows down. Then I started digging into your code, I found couple of
> things I can change like you guys are using DOM Parser which is Memory
> intensive , So started changing your code to use SAXParser and also I need
> to changing couple of things in your DOMUtils code too. So now it works
> very fast like in seconds I can see output. So I would like share my
> code and see what you guys think , also wants to contribute to
> development. Not sure how to proceed can some body help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Thanks Scott. To answer your questions I am using Xalan 2.2 and have tested the changes for Pay loads around 50 Kb - 300 kb . It works great in my environment using Tomcat 3.2.1 . Also I made same changes to WebSphere 4.1 Soap distribution, its work there too.
Let me know if you need more info about my environment.
Thanks,
Raj.
Scott Nichol wrote:Raj,
In case you missed it, I committed a variation of your changes last night.
The biggest different is that the DocumentBuilder method is still there and
is the default, but the method to use can be specified for each Call. I
want to run some tests to understand the performance impact in various
scenarios.
Scott Nichol
----- Original Message -----
From: "Scott Nichol"
To:
Sent: Wednesday, July 24, 2002 5:58 PM
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
> Raj,
>
> I am working on integrating your changes into the current CVS code, but I
> have had some problems while testing. I am using Xalan 2.3.1. I am
finding
> that, at least for small payloads, using the SAXSource -> DOMResult
> transform takes longer than using the DOM Parser. I am also getting a
SOAP
> fault on the client when running the addressbook sample.
>
> What parser/transformer were you using? Were you testing with small or
> large payloads?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "yellapragada rajasekhar"
> To:
> Sent: Wednesday, July 03, 2002 1:17 PM
> Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
>
> >
> > Scott,
> > Sorry It took so long to reply. Anyway I have generated patch for two
> files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
> these files are attached to the mail. And here is the patch file
> > diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> > 76a77,84
> > > import javax.xml.transform.dom.DOMResult; // JAXP
> > > import javax.xml.transform.sax.SAXSource; // JAXP
> > > import javax.xml.transform.TransformerFactory; // JAXP
> > > import javax.xml.transform.Transformer; // JAXP
> > > import javax.xml.transform.dom.DOMSource; // JAXP
> > > import javax.xml.transform.stream.StreamResult; // JAXP
> > >
> > >
> > 215,216c223,243
> > < Document respDoc =
> > < xdb.parse(new InputSource(new StringReader(payloadStr)));
> > ---
> > > Document respDoc = null;
> > > // author Raj Yellapragada
> > > // Here I have generated SAX document instead of DOM document using
> Transformation functions in
> > > // JAXP tools. This is way faster than DOM parser (xdb).
> > > // Document respDoc =
> > > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > > // Document document = null;
> > > try
> > > {
> > >
> > > DOMResult output = new DOMResult();
> > > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > > Transformer idTransform = xformFactory.newTransformer();
> > > idTransform.transform(new SAXSource(new InputSource(new
> StringReader(payloadStr))), output);
> > > respDoc = (Document) output.getNode();
> > > }
> > > catch(Exception e)
> > > {
> > > System.out.println("Error in Transformation of DOM Document to Sax
> Document " + e);
> > > }
> > >
> > 234d260
> > <
> > 248,253c274,279
> > < catch (SAXException e)
> > < {
> > < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > < "Parsing error, response was:\n"
> +e.getMessage(),
> > < e);
> > < }
> > ---
> > > // catch (SAXException e)
> > > // {
> > > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > > // "Parsing error, response was:\n"
> +e.getMessage(),
> > > // e);
> > > // }
> > diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> > 70c70
> > < private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > ---
> > > private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > 106d105
> > <
> > 249a249
> > >
> > 252,255c252
> > < Element tempEl = (Element) tempNode;
> > < String namespaceURI = (prefix == null)
> > < ? getAttribute (tempEl, "xmlns")
> > < : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > ---
> > > Element tempEl = (Element) tempNode;
> > 257,264c254,276
> > < if (namespaceURI != null)
> > < {
> > < return namespaceURI;
> > < }
> > < else
> > < {
> > < tempNode = tempEl.getParentNode ();
> > < }
> > ---
> > > String namespaceURI ;
> > >
> > > try
> > > {
> > > namespaceURI = (prefix == null)
> > > ? getAttribute (tempEl, "xmlns")
> > > : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > > }
> > > // Raj Yellapragada Here I am checking for NullPointerException and
if
> it is I am using
> > > // Element getattribute method to get to namespaceURI.
> > > catch(java.lang.NullPointerException e)
> > > {
> > > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > > }
> > > if (namespaceURI != null)
> > > {
> > >
> > > return namespaceURI;
> > > }
> > > else
> > > {
> > > tempNode = tempEl.getParentNode ();
> > > }
> > 266c278
> > <
> > ---
> > >
> >
> >
> > Scott Nichol wrote: Raj,
> >
> > Are you still interested in contributing this code?
> >
> > Scott Nichol
> >
> > --- yellapragada rajasekhar wrote:
> > >
> > > Hi ,
> > >
> > > My Name is Raj . I work for Insurance Company in
> > > Scottsdale. Recently
> > > my company asked me to look into web services. I
> > > started downloading
> > > SOAP stuff from apache site, I wrote small programs
> > > every thing works
> > > great. But when I really started doing prototype of
> > > an existing application
> > > , it doesn't seem to be working right. Like if Data
> > > over the wire from
> > > Database to Tomcat/SOAP server to Browser is minimal
> > > then it
> > > takes few seconds to process, but if data is huge (>
> > > 300 Kb) then it really
> > > slows down. Then I started digging into your code, I
> > > found couple of
> > > things I can change like you guys are using DOM
> > > Parser which is Memory
> > > intensive , So started changing your code to use
> > > SAXParser and also I need
> > > to changing couple of things in your DOMUtils code
> > > too. So now it works
> > > very fast like in seconds I can see output. So I
> > > would like share my
> > > code and see what you guys think , also wants to
> > > contribute to
> > > development. Not sure how to proceed can some body
> > > help me on this...
> > >
> > >
> > >
> > > Thanks,
> > > Raj
> > >
> > >
> > >
> > >
> > >
> > > Raja Sekhar.Y
> > Software Eng.
> >
> > >
> > >
> > > ---------------------------------
> > > Do You Yahoo!?
> > > LAUNCH - Your Yahoo! Music Experience
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> >
> > Raja Sekhar.Y
Software Eng.
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > New! SBC Yahoo! Dial - 1st Month Free & unlimited access
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> > --
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
>
>
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
Yahoo! Health - Feel better, live better
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Thanks Scott. To answer your questions I am using Xalan 2.2 and have tested the changes for Pay loads around 50 Kb - 300 kb . It works great in my environment using Tomcat 3.2.1 . Also I made same changes to WebSphere 4.1 Soap distribution, its work there too.
Let me know if you need more info about my environment.
Thanks,
Raj.
Scott Nichol wrote:Raj,
In case you missed it, I committed a variation of your changes last night.
The biggest different is that the DocumentBuilder method is still there and
is the default, but the method to use can be specified for each Call. I
want to run some tests to understand the performance impact in various
scenarios.
Scott Nichol
----- Original Message -----
From: "Scott Nichol"
To:
Sent: Wednesday, July 24, 2002 5:58 PM
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
> Raj,
>
> I am working on integrating your changes into the current CVS code, but I
> have had some problems while testing. I am using Xalan 2.3.1. I am
finding
> that, at least for small payloads, using the SAXSource -> DOMResult
> transform takes longer than using the DOM Parser. I am also getting a
SOAP
> fault on the client when running the addressbook sample.
>
> What parser/transformer were you using? Were you testing with small or
> large payloads?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "yellapragada rajasekhar"
> To:
> Sent: Wednesday, July 03, 2002 1:17 PM
> Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
>
> >
> > Scott,
> > Sorry It took so long to reply. Anyway I have generated patch for two
> files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
> these files are attached to the mail. And here is the patch file
> > diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> > 76a77,84
> > > import javax.xml.transform.dom.DOMResult; // JAXP
> > > import javax.xml.transform.sax.SAXSource; // JAXP
> > > import javax.xml.transform.TransformerFactory; // JAXP
> > > import javax.xml.transform.Transformer; // JAXP
> > > import javax.xml.transform.dom.DOMSource; // JAXP
> > > import javax.xml.transform.stream.StreamResult; // JAXP
> > >
> > >
> > 215,216c223,243
> > < Document respDoc =
> > < xdb.parse(new InputSource(new StringReader(payloadStr)));
> > ---
> > > Document respDoc = null;
> > > // author Raj Yellapragada
> > > // Here I have generated SAX document instead of DOM document using
> Transformation functions in
> > > // JAXP tools. This is way faster than DOM parser (xdb).
> > > // Document respDoc =
> > > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > > // Document document = null;
> > > try
> > > {
> > >
> > > DOMResult output = new DOMResult();
> > > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > > Transformer idTransform = xformFactory.newTransformer();
> > > idTransform.transform(new SAXSource(new InputSource(new
> StringReader(payloadStr))), output);
> > > respDoc = (Document) output.getNode();
> > > }
> > > catch(Exception e)
> > > {
> > > System.out.println("Error in Transformation of DOM Document to Sax
> Document " + e);
> > > }
> > >
> > 234d260
> > <
> > 248,253c274,279
> > < catch (SAXException e)
> > < {
> > < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > < "Parsing error, response was:\n"
> +e.getMessage(),
> > < e);
> > < }
> > ---
> > > // catch (SAXException e)
> > > // {
> > > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > > // "Parsing error, response was:\n"
> +e.getMessage(),
> > > // e);
> > > // }
> > diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> > 70c70
> > < private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > ---
> > > private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > 106d105
> > <
> > 249a249
> > >
> > 252,255c252
> > < Element tempEl = (Element) tempNode;
> > < String namespaceURI = (prefix == null)
> > < ? getAttribute (tempEl, "xmlns")
> > < : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > ---
> > > Element tempEl = (Element) tempNode;
> > 257,264c254,276
> > < if (namespaceURI != null)
> > < {
> > < return namespaceURI;
> > < }
> > < else
> > < {
> > < tempNode = tempEl.getParentNode ();
> > < }
> > ---
> > > String namespaceURI ;
> > >
> > > try
> > > {
> > > namespaceURI = (prefix == null)
> > > ? getAttribute (tempEl, "xmlns")
> > > : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > > }
> > > // Raj Yellapragada Here I am checking for NullPointerException and
if
> it is I am using
> > > // Element getattribute method to get to namespaceURI.
> > > catch(java.lang.NullPointerException e)
> > > {
> > > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > > }
> > > if (namespaceURI != null)
> > > {
> > >
> > > return namespaceURI;
> > > }
> > > else
> > > {
> > > tempNode = tempEl.getParentNode ();
> > > }
> > 266c278
> > <
> > ---
> > >
> >
> >
> > Scott Nichol wrote: Raj,
> >
> > Are you still interested in contributing this code?
> >
> > Scott Nichol
> >
> > --- yellapragada rajasekhar wrote:
> > >
> > > Hi ,
> > >
> > > My Name is Raj . I work for Insurance Company in
> > > Scottsdale. Recently
> > > my company asked me to look into web services. I
> > > started downloading
> > > SOAP stuff from apache site, I wrote small programs
> > > every thing works
> > > great. But when I really started doing prototype of
> > > an existing application
> > > , it doesn't seem to be working right. Like if Data
> > > over the wire from
> > > Database to Tomcat/SOAP server to Browser is minimal
> > > then it
> > > takes few seconds to process, but if data is huge (>
> > > 300 Kb) then it really
> > > slows down. Then I started digging into your code, I
> > > found couple of
> > > things I can change like you guys are using DOM
> > > Parser which is Memory
> > > intensive , So started changing your code to use
> > > SAXParser and also I need
> > > to changing couple of things in your DOMUtils code
> > > too. So now it works
> > > very fast like in seconds I can see output. So I
> > > would like share my
> > > code and see what you guys think , also wants to
> > > contribute to
> > > development. Not sure how to proceed can some body
> > > help me on this...
> > >
> > >
> > >
> > > Thanks,
> > > Raj
> > >
> > >
> > >
> > >
> > >
> > > Raja Sekhar.Y
> > Software Eng.
> >
> > >
> > >
> > > ---------------------------------
> > > Do You Yahoo!?
> > > LAUNCH - Your Yahoo! Music Experience
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> >
> > Raja Sekhar.Y
Software Eng.
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > New! SBC Yahoo! Dial - 1st Month Free & unlimited access
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> > --
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
>
>
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
Yahoo! Health - Feel better, live better
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sn...@scottnichol.com>.
Raj,
In case you missed it, I committed a variation of your changes last night.
The biggest different is that the DocumentBuilder method is still there and
is the default, but the method to use can be specified for each Call. I
want to run some tests to understand the performance impact in various
scenarios.
Scott Nichol
----- Original Message -----
From: "Scott Nichol" <sn...@scottnichol.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 5:58 PM
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
> Raj,
>
> I am working on integrating your changes into the current CVS code, but I
> have had some problems while testing. I am using Xalan 2.3.1. I am
finding
> that, at least for small payloads, using the SAXSource -> DOMResult
> transform takes longer than using the DOM Parser. I am also getting a
SOAP
> fault on the client when running the addressbook sample.
>
> What parser/transformer were you using? Were you testing with small or
> large payloads?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "yellapragada rajasekhar" <ra...@yahoo.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 03, 2002 1:17 PM
> Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
>
> >
> > Scott,
> > Sorry It took so long to reply. Anyway I have generated patch for two
> files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
> these files are attached to the mail. And here is the patch file
> > diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> > 76a77,84
> > > import javax.xml.transform.dom.DOMResult; // JAXP
> > > import javax.xml.transform.sax.SAXSource; // JAXP
> > > import javax.xml.transform.TransformerFactory; // JAXP
> > > import javax.xml.transform.Transformer; // JAXP
> > > import javax.xml.transform.dom.DOMSource; // JAXP
> > > import javax.xml.transform.stream.StreamResult; // JAXP
> > >
> > >
> > 215,216c223,243
> > < Document respDoc =
> > < xdb.parse(new InputSource(new StringReader(payloadStr)));
> > ---
> > > Document respDoc = null;
> > > // author Raj Yellapragada
> > > // Here I have generated SAX document instead of DOM document using
> Transformation functions in
> > > // JAXP tools. This is way faster than DOM parser (xdb).
> > > // Document respDoc =
> > > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > > // Document document = null;
> > > try
> > > {
> > >
> > > DOMResult output = new DOMResult();
> > > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > > Transformer idTransform = xformFactory.newTransformer();
> > > idTransform.transform(new SAXSource(new InputSource(new
> StringReader(payloadStr))), output);
> > > respDoc = (Document) output.getNode();
> > > }
> > > catch(Exception e)
> > > {
> > > System.out.println("Error in Transformation of DOM Document to Sax
> Document " + e);
> > > }
> > >
> > 234d260
> > <
> > 248,253c274,279
> > < catch (SAXException e)
> > < {
> > < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > < "Parsing error, response was:\n"
> +e.getMessage(),
> > < e);
> > < }
> > ---
> > > // catch (SAXException e)
> > > // {
> > > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > > // "Parsing error, response was:\n"
> +e.getMessage(),
> > > // e);
> > > // }
> > diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> > 70c70
> > < private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > ---
> > > private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > 106d105
> > <
> > 249a249
> > >
> > 252,255c252
> > < Element tempEl = (Element) tempNode;
> > < String namespaceURI = (prefix == null)
> > < ? getAttribute (tempEl, "xmlns")
> > < : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > ---
> > > Element tempEl = (Element) tempNode;
> > 257,264c254,276
> > < if (namespaceURI != null)
> > < {
> > < return namespaceURI;
> > < }
> > < else
> > < {
> > < tempNode = tempEl.getParentNode ();
> > < }
> > ---
> > > String namespaceURI ;
> > >
> > > try
> > > {
> > > namespaceURI = (prefix == null)
> > > ? getAttribute (tempEl, "xmlns")
> > > : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > > }
> > > // Raj Yellapragada Here I am checking for NullPointerException and
if
> it is I am using
> > > // Element getattribute method to get to namespaceURI.
> > > catch(java.lang.NullPointerException e)
> > > {
> > > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > > }
> > > if (namespaceURI != null)
> > > {
> > >
> > > return namespaceURI;
> > > }
> > > else
> > > {
> > > tempNode = tempEl.getParentNode ();
> > > }
> > 266c278
> > <
> > ---
> > >
> >
> >
> > Scott Nichol <sc...@yahoo.com> wrote: Raj,
> >
> > Are you still interested in contributing this code?
> >
> > Scott Nichol
> >
> > --- yellapragada rajasekhar wrote:
> > >
> > > Hi ,
> > >
> > > My Name is Raj . I work for Insurance Company in
> > > Scottsdale. Recently
> > > my company asked me to look into web services. I
> > > started downloading
> > > SOAP stuff from apache site, I wrote small programs
> > > every thing works
> > > great. But when I really started doing prototype of
> > > an existing application
> > > , it doesn't seem to be working right. Like if Data
> > > over the wire from
> > > Database to Tomcat/SOAP server to Browser is minimal
> > > then it
> > > takes few seconds to process, but if data is huge (>
> > > 300 Kb) then it really
> > > slows down. Then I started digging into your code, I
> > > found couple of
> > > things I can change like you guys are using DOM
> > > Parser which is Memory
> > > intensive , So started changing your code to use
> > > SAXParser and also I need
> > > to changing couple of things in your DOMUtils code
> > > too. So now it works
> > > very fast like in seconds I can see output. So I
> > > would like share my
> > > code and see what you guys think , also wants to
> > > contribute to
> > > development. Not sure how to proceed can some body
> > > help me on this...
> > >
> > >
> > >
> > > Thanks,
> > > Raj
> > >
> > >
> > >
> > >
> > >
> > > Raja Sekhar.Y
> > Software Eng.
> >
> > >
> > >
> > > ---------------------------------
> > > Do You Yahoo!?
> > > LAUNCH - Your Yahoo! Music Experience
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> >
> > Raja Sekhar.Y<BR>Software Eng.<BR>
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > New! SBC Yahoo! Dial - 1st Month Free & unlimited access
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sn...@scottnichol.com>.
Raj,
In case you missed it, I committed a variation of your changes last night.
The biggest different is that the DocumentBuilder method is still there and
is the default, but the method to use can be specified for each Call. I
want to run some tests to understand the performance impact in various
scenarios.
Scott Nichol
----- Original Message -----
From: "Scott Nichol" <sn...@scottnichol.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 24, 2002 5:58 PM
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
> Raj,
>
> I am working on integrating your changes into the current CVS code, but I
> have had some problems while testing. I am using Xalan 2.3.1. I am
finding
> that, at least for small payloads, using the SAXSource -> DOMResult
> transform takes longer than using the DOM Parser. I am also getting a
SOAP
> fault on the client when running the addressbook sample.
>
> What parser/transformer were you using? Were you testing with small or
> large payloads?
>
> Scott Nichol
>
> ----- Original Message -----
> From: "yellapragada rajasekhar" <ra...@yahoo.com>
> To: <so...@xml.apache.org>
> Sent: Wednesday, July 03, 2002 1:17 PM
> Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
>
> >
> > Scott,
> > Sorry It took so long to reply. Anyway I have generated patch for two
> files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
> these files are attached to the mail. And here is the patch file
> > diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> > 76a77,84
> > > import javax.xml.transform.dom.DOMResult; // JAXP
> > > import javax.xml.transform.sax.SAXSource; // JAXP
> > > import javax.xml.transform.TransformerFactory; // JAXP
> > > import javax.xml.transform.Transformer; // JAXP
> > > import javax.xml.transform.dom.DOMSource; // JAXP
> > > import javax.xml.transform.stream.StreamResult; // JAXP
> > >
> > >
> > 215,216c223,243
> > < Document respDoc =
> > < xdb.parse(new InputSource(new StringReader(payloadStr)));
> > ---
> > > Document respDoc = null;
> > > // author Raj Yellapragada
> > > // Here I have generated SAX document instead of DOM document using
> Transformation functions in
> > > // JAXP tools. This is way faster than DOM parser (xdb).
> > > // Document respDoc =
> > > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > > // Document document = null;
> > > try
> > > {
> > >
> > > DOMResult output = new DOMResult();
> > > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > > Transformer idTransform = xformFactory.newTransformer();
> > > idTransform.transform(new SAXSource(new InputSource(new
> StringReader(payloadStr))), output);
> > > respDoc = (Document) output.getNode();
> > > }
> > > catch(Exception e)
> > > {
> > > System.out.println("Error in Transformation of DOM Document to Sax
> Document " + e);
> > > }
> > >
> > 234d260
> > <
> > 248,253c274,279
> > < catch (SAXException e)
> > < {
> > < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > < "Parsing error, response was:\n"
> +e.getMessage(),
> > < e);
> > < }
> > ---
> > > // catch (SAXException e)
> > > // {
> > > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > > // "Parsing error, response was:\n"
> +e.getMessage(),
> > > // e);
> > > // }
> > diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> > 70c70
> > < private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > ---
> > > private static String NS_URI_XMLNS =
"http://www.w3.org/2000/xmlns/";
> > 106d105
> > <
> > 249a249
> > >
> > 252,255c252
> > < Element tempEl = (Element) tempNode;
> > < String namespaceURI = (prefix == null)
> > < ? getAttribute (tempEl, "xmlns")
> > < : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > ---
> > > Element tempEl = (Element) tempNode;
> > 257,264c254,276
> > < if (namespaceURI != null)
> > < {
> > < return namespaceURI;
> > < }
> > < else
> > < {
> > < tempNode = tempEl.getParentNode ();
> > < }
> > ---
> > > String namespaceURI ;
> > >
> > > try
> > > {
> > > namespaceURI = (prefix == null)
> > > ? getAttribute (tempEl, "xmlns")
> > > : getAttributeNS (tempEl, NS_URI_XMLNS,
> prefix);
> > > }
> > > // Raj Yellapragada Here I am checking for NullPointerException and
if
> it is I am using
> > > // Element getattribute method to get to namespaceURI.
> > > catch(java.lang.NullPointerException e)
> > > {
> > > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > > }
> > > if (namespaceURI != null)
> > > {
> > >
> > > return namespaceURI;
> > > }
> > > else
> > > {
> > > tempNode = tempEl.getParentNode ();
> > > }
> > 266c278
> > <
> > ---
> > >
> >
> >
> > Scott Nichol <sc...@yahoo.com> wrote: Raj,
> >
> > Are you still interested in contributing this code?
> >
> > Scott Nichol
> >
> > --- yellapragada rajasekhar wrote:
> > >
> > > Hi ,
> > >
> > > My Name is Raj . I work for Insurance Company in
> > > Scottsdale. Recently
> > > my company asked me to look into web services. I
> > > started downloading
> > > SOAP stuff from apache site, I wrote small programs
> > > every thing works
> > > great. But when I really started doing prototype of
> > > an existing application
> > > , it doesn't seem to be working right. Like if Data
> > > over the wire from
> > > Database to Tomcat/SOAP server to Browser is minimal
> > > then it
> > > takes few seconds to process, but if data is huge (>
> > > 300 Kb) then it really
> > > slows down. Then I started digging into your code, I
> > > found couple of
> > > things I can change like you guys are using DOM
> > > Parser which is Memory
> > > intensive , So started changing your code to use
> > > SAXParser and also I need
> > > to changing couple of things in your DOMUtils code
> > > too. So now it works
> > > very fast like in seconds I can see output. So I
> > > would like share my
> > > code and see what you guys think , also wants to
> > > contribute to
> > > development. Not sure how to proceed can some body
> > > help me on this...
> > >
> > >
> > >
> > > Thanks,
> > > Raj
> > >
> > >
> > >
> > >
> > >
> > > Raja Sekhar.Y
> > Software Eng.
> >
> > >
> > >
> > > ---------------------------------
> > > Do You Yahoo!?
> > > LAUNCH - Your Yahoo! Music Experience
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! - Official partner of 2002 FIFA World Cup
> > http://fifaworldcup.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> > For additional commands, e-mail:
> >
> >
> > Raja Sekhar.Y<BR>Software Eng.<BR>
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > New! SBC Yahoo! Dial - 1st Month Free & unlimited access
>
>
> --------------------------------------------------------------------------
--
> ----
>
>
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sn...@scottnichol.com>.
Raj,
I am working on integrating your changes into the current CVS code, but I
have had some problems while testing. I am using Xalan 2.3.1. I am finding
that, at least for small payloads, using the SAXSource -> DOMResult
transform takes longer than using the DOM Parser. I am also getting a SOAP
fault on the client when running the addressbook sample.
What parser/transformer were you using? Were you testing with small or
large payloads?
Scott Nichol
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 03, 2002 1:17 PM
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
> Scott,
> Sorry It took so long to reply. Anyway I have generated patch for two
files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
these files are attached to the mail. And here is the patch file
> diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> 76a77,84
> > import javax.xml.transform.dom.DOMResult; // JAXP
> > import javax.xml.transform.sax.SAXSource; // JAXP
> > import javax.xml.transform.TransformerFactory; // JAXP
> > import javax.xml.transform.Transformer; // JAXP
> > import javax.xml.transform.dom.DOMSource; // JAXP
> > import javax.xml.transform.stream.StreamResult; // JAXP
> >
> >
> 215,216c223,243
> < Document respDoc =
> < xdb.parse(new InputSource(new StringReader(payloadStr)));
> ---
> > Document respDoc = null;
> > // author Raj Yellapragada
> > // Here I have generated SAX document instead of DOM document using
Transformation functions in
> > // JAXP tools. This is way faster than DOM parser (xdb).
> > // Document respDoc =
> > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > // Document document = null;
> > try
> > {
> >
> > DOMResult output = new DOMResult();
> > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > Transformer idTransform = xformFactory.newTransformer();
> > idTransform.transform(new SAXSource(new InputSource(new
StringReader(payloadStr))), output);
> > respDoc = (Document) output.getNode();
> > }
> > catch(Exception e)
> > {
> > System.out.println("Error in Transformation of DOM Document to Sax
Document " + e);
> > }
> >
> 234d260
> <
> 248,253c274,279
> < catch (SAXException e)
> < {
> < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> < "Parsing error, response was:\n"
+e.getMessage(),
> < e);
> < }
> ---
> > // catch (SAXException e)
> > // {
> > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > // "Parsing error, response was:\n"
+e.getMessage(),
> > // e);
> > // }
> diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> 70c70
> < private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> ---
> > private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> 106d105
> <
> 249a249
> >
> 252,255c252
> < Element tempEl = (Element) tempNode;
> < String namespaceURI = (prefix == null)
> < ? getAttribute (tempEl, "xmlns")
> < : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> ---
> > Element tempEl = (Element) tempNode;
> 257,264c254,276
> < if (namespaceURI != null)
> < {
> < return namespaceURI;
> < }
> < else
> < {
> < tempNode = tempEl.getParentNode ();
> < }
> ---
> > String namespaceURI ;
> >
> > try
> > {
> > namespaceURI = (prefix == null)
> > ? getAttribute (tempEl, "xmlns")
> > : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> > }
> > // Raj Yellapragada Here I am checking for NullPointerException and if
it is I am using
> > // Element getattribute method to get to namespaceURI.
> > catch(java.lang.NullPointerException e)
> > {
> > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > }
> > if (namespaceURI != null)
> > {
> >
> > return namespaceURI;
> > }
> > else
> > {
> > tempNode = tempEl.getParentNode ();
> > }
> 266c278
> <
> ---
> >
>
>
> Scott Nichol <sc...@yahoo.com> wrote: Raj,
>
> Are you still interested in contributing this code?
>
> Scott Nichol
>
> --- yellapragada rajasekhar wrote:
> >
> > Hi ,
> >
> > My Name is Raj . I work for Insurance Company in
> > Scottsdale. Recently
> > my company asked me to look into web services. I
> > started downloading
> > SOAP stuff from apache site, I wrote small programs
> > every thing works
> > great. But when I really started doing prototype of
> > an existing application
> > , it doesn't seem to be working right. Like if Data
> > over the wire from
> > Database to Tomcat/SOAP server to Browser is minimal
> > then it
> > takes few seconds to process, but if data is huge (>
> > 300 Kb) then it really
> > slows down. Then I started digging into your code, I
> > found couple of
> > things I can change like you guys are using DOM
> > Parser which is Memory
> > intensive , So started changing your code to use
> > SAXParser and also I need
> > to changing couple of things in your DOMUtils code
> > too. So now it works
> > very fast like in seconds I can see output. So I
> > would like share my
> > code and see what you guys think , also wants to
> > contribute to
> > development. Not sure how to proceed can some body
> > help me on this...
> >
> >
> >
> > Thanks,
> > Raj
> >
> >
> >
> >
> >
> > Raja Sekhar.Y
> Software Eng.
>
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > LAUNCH - Your Yahoo! Music Experience
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> New! SBC Yahoo! Dial - 1st Month Free & unlimited access
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sn...@scottnichol.com>.
Raj,
I am working on integrating your changes into the current CVS code, but I
have had some problems while testing. I am using Xalan 2.3.1. I am finding
that, at least for small payloads, using the SAXSource -> DOMResult
transform takes longer than using the DOM Parser. I am also getting a SOAP
fault on the client when running the addressbook sample.
What parser/transformer were you using? Were you testing with small or
large payloads?
Scott Nichol
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Wednesday, July 03, 2002 1:17 PM
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
> Scott,
> Sorry It took so long to reply. Anyway I have generated patch for two
files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
these files are attached to the mail. And here is the patch file
> diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> 76a77,84
> > import javax.xml.transform.dom.DOMResult; // JAXP
> > import javax.xml.transform.sax.SAXSource; // JAXP
> > import javax.xml.transform.TransformerFactory; // JAXP
> > import javax.xml.transform.Transformer; // JAXP
> > import javax.xml.transform.dom.DOMSource; // JAXP
> > import javax.xml.transform.stream.StreamResult; // JAXP
> >
> >
> 215,216c223,243
> < Document respDoc =
> < xdb.parse(new InputSource(new StringReader(payloadStr)));
> ---
> > Document respDoc = null;
> > // author Raj Yellapragada
> > // Here I have generated SAX document instead of DOM document using
Transformation functions in
> > // JAXP tools. This is way faster than DOM parser (xdb).
> > // Document respDoc =
> > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > // Document document = null;
> > try
> > {
> >
> > DOMResult output = new DOMResult();
> > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > Transformer idTransform = xformFactory.newTransformer();
> > idTransform.transform(new SAXSource(new InputSource(new
StringReader(payloadStr))), output);
> > respDoc = (Document) output.getNode();
> > }
> > catch(Exception e)
> > {
> > System.out.println("Error in Transformation of DOM Document to Sax
Document " + e);
> > }
> >
> 234d260
> <
> 248,253c274,279
> < catch (SAXException e)
> < {
> < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> < "Parsing error, response was:\n"
+e.getMessage(),
> < e);
> < }
> ---
> > // catch (SAXException e)
> > // {
> > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > // "Parsing error, response was:\n"
+e.getMessage(),
> > // e);
> > // }
> diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> 70c70
> < private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> ---
> > private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> 106d105
> <
> 249a249
> >
> 252,255c252
> < Element tempEl = (Element) tempNode;
> < String namespaceURI = (prefix == null)
> < ? getAttribute (tempEl, "xmlns")
> < : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> ---
> > Element tempEl = (Element) tempNode;
> 257,264c254,276
> < if (namespaceURI != null)
> < {
> < return namespaceURI;
> < }
> < else
> < {
> < tempNode = tempEl.getParentNode ();
> < }
> ---
> > String namespaceURI ;
> >
> > try
> > {
> > namespaceURI = (prefix == null)
> > ? getAttribute (tempEl, "xmlns")
> > : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> > }
> > // Raj Yellapragada Here I am checking for NullPointerException and if
it is I am using
> > // Element getattribute method to get to namespaceURI.
> > catch(java.lang.NullPointerException e)
> > {
> > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > }
> > if (namespaceURI != null)
> > {
> >
> > return namespaceURI;
> > }
> > else
> > {
> > tempNode = tempEl.getParentNode ();
> > }
> 266c278
> <
> ---
> >
>
>
> Scott Nichol <sc...@yahoo.com> wrote: Raj,
>
> Are you still interested in contributing this code?
>
> Scott Nichol
>
> --- yellapragada rajasekhar wrote:
> >
> > Hi ,
> >
> > My Name is Raj . I work for Insurance Company in
> > Scottsdale. Recently
> > my company asked me to look into web services. I
> > started downloading
> > SOAP stuff from apache site, I wrote small programs
> > every thing works
> > great. But when I really started doing prototype of
> > an existing application
> > , it doesn't seem to be working right. Like if Data
> > over the wire from
> > Database to Tomcat/SOAP server to Browser is minimal
> > then it
> > takes few seconds to process, but if data is huge (>
> > 300 Kb) then it really
> > slows down. Then I started digging into your code, I
> > found couple of
> > things I can change like you guys are using DOM
> > Parser which is Memory
> > intensive , So started changing your code to use
> > SAXParser and also I need
> > to changing couple of things in your DOMUtils code
> > too. So now it works
> > very fast like in seconds I can see output. So I
> > would like share my
> > code and see what you guys think , also wants to
> > contribute to
> > development. Not sure how to proceed can some body
> > help me on this...
> >
> >
> >
> > Thanks,
> > Raj
> >
> >
> >
> >
> >
> > Raja Sekhar.Y
> Software Eng.
>
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > LAUNCH - Your Yahoo! Music Experience
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> New! SBC Yahoo! Dial - 1st Month Free & unlimited access
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sn...@scottnichol.com>.
I'm on vacation this week and will perhaps get to this next week.
Scott Nichol
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Monday, July 15, 2002 15:39
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
> Scott,
> Please let me know the status on this one .
> Thanks,
> Raj.
>
> yellapragada rajasekhar <ra...@yahoo.com> wrote:
> Scott,
> Sorry It took so long to reply. Anyway I have generated patch for two
files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
these files are attached to the mail. And here is the patch file
> diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> 76a77,84
> > import javax.xml.transform.dom.DOMResult; // JAXP
> > import javax.xml.transform.sax.SAXSource; // JAXP
> > import javax.xml.transform.TransformerFactory; // JAXP
> > import javax.xml.transform.Transformer; // JAXP
> > import javax.xml.transform.dom.DOMSource; // JAXP
> > import javax.xml.transform.stream.StreamResult; // JAXP
> >
> >
> 215,216c223,243
> < Document respDoc =
> < xdb.parse(new InputSource(new StringReader(payloadStr)));
> ---
> > Document respDoc = null;
> > // author Raj Yellapragada
> > // Here I have generated SAX document instead of DOM document using
Transformation functions in
> > // JAXP tools. This is way faster than DOM parser (xdb).
> > // Document respDoc =
> > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > // Document document = null;
> > try
> > {
> >
> > DOMResult output = new DOMResult();
> > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > Transformer idTransform = xformFactory.newTransformer();
> > idTransform.transform(new SAXSource(new InputSource(new
StringReader(payloadStr))), output);
> > respDoc = (Document) output.getNode();
> > }
> > catch(Exception e)
> > {
> > System.out.println("Error in Transformation of DOM Document to Sax
Document " + e);
> > }
> >
> 234d260
> <
> 248,253c274,279
> < catch (SAXException e)
> < {
> < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> < "Parsing error, response was:\n"
+e.getMessage(),
> < e);
> < }
> ---
> > // catch (SAXException e)
> > // {
> > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > // "Parsing error, response was:\n"
+e.getMessage(),
> > // e);
> > // }
> diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> 70c70
> < private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> ---
> > private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> 106d105
> <
> 249a249
> >
> 252,255c252
> < Element tempEl = (Element) tempNode;
> < String namespaceURI = (prefix == null)
> < ? getAttribute (tempEl, "xmlns")
> < : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> ---
> > Element tempEl = (Element) tempNode;
> 257,264c254,276
> < if (namespaceURI != null)
> < {
> < return namespaceURI;
> < }
> < else
> < {
> < tempNode = tempEl.getParentNode ();
> < }
> ---
> > String namespaceURI ;
> >
> > try
> > {
> > namespaceURI = (prefix == null)
> > ? getAttribute (tempEl, "xmlns")
> > : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> > }
> > // Raj Yellapragada Here I am checking for NullPointerException and if
it is I am using
> > // Element getattribute method to get to namespaceURI.
> > catch(java.lang.NullPointerException e)
> > {
> > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > }
> > if (namespaceURI != null)
> > {
> >
> > return namespaceURI;
> > }
> > else
> > {
> > tempNode = tempEl.getParentNode ();
> > }
> 266c278
> <
> ---
> >
>
>
> Scott Nichol <sc...@yahoo.com> wrote: Raj,
>
> Are you still interested in contributing this code?
>
> Scott Nichol
>
> --- yellapragada rajasekhar wrote:
> >
> > Hi ,
> >
> > My Name is Raj . I work for Insurance Company in
> > Scottsdale. Recently
> > my company asked me to look into web services. I
> > started downloading
> > SOAP stuff from apache site, I wrote small programs
> > every thing works
> > great. But when I really started doing prototype of
> > an existing application
> > , it doesn't seem to be working right. Like if Data
> > over the wire from
> > Database to Tomcat/SOAP server to Browser is minimal
> > then it
> > takes few seconds to process, but if data is huge (>
> > 300 Kb) then it really
> > slows down. Then I started digging into your code, I
> > found couple of
> > things I can change like you guys are using DOM
> > Parser which is Memory
> > intensive , So started changing your code to use
> > SAXParser and also I need
> > to changing couple of things in your DOMUtils code
> > too. So now it works
> > very fast like in seconds I can see output. So I
> > would like share my
> > code and see what you guys think , also wants to
> > contribute to
> > development. Not sure how to proceed can some body
> > help me on this...
> >
> >
> >
> > Thanks,
> > Raj
> >
> >
> >
> >
> >
> > Raja Sekhar.Y
> Software Eng.
>
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > LAUNCH - Your Yahoo! Music Experience
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> New! SBC Yahoo! Dial - 1st Month Free & unlimited access--
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> Yahoo! Autos - Get free new car price quotes
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sn...@scottnichol.com>.
I'm on vacation this week and will perhaps get to this next week.
Scott Nichol
----- Original Message -----
From: "yellapragada rajasekhar" <ra...@yahoo.com>
To: <so...@xml.apache.org>
Sent: Monday, July 15, 2002 15:39
Subject: Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
>
> Scott,
> Please let me know the status on this one .
> Thanks,
> Raj.
>
> yellapragada rajasekhar <ra...@yahoo.com> wrote:
> Scott,
> Sorry It took so long to reply. Anyway I have generated patch for two
files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils,
these files are attached to the mail. And here is the patch file
> diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
> 76a77,84
> > import javax.xml.transform.dom.DOMResult; // JAXP
> > import javax.xml.transform.sax.SAXSource; // JAXP
> > import javax.xml.transform.TransformerFactory; // JAXP
> > import javax.xml.transform.Transformer; // JAXP
> > import javax.xml.transform.dom.DOMSource; // JAXP
> > import javax.xml.transform.stream.StreamResult; // JAXP
> >
> >
> 215,216c223,243
> < Document respDoc =
> < xdb.parse(new InputSource(new StringReader(payloadStr)));
> ---
> > Document respDoc = null;
> > // author Raj Yellapragada
> > // Here I have generated SAX document instead of DOM document using
Transformation functions in
> > // JAXP tools. This is way faster than DOM parser (xdb).
> > // Document respDoc =
> > // xdb.parse(new InputSource(new StringReader(payloadStr)));
> > // Document document = null;
> > try
> > {
> >
> > DOMResult output = new DOMResult();
> > TransformerFactory xformFactory = TransformerFactory.newInstance();
> > Transformer idTransform = xformFactory.newTransformer();
> > idTransform.transform(new SAXSource(new InputSource(new
StringReader(payloadStr))), output);
> > respDoc = (Document) output.getNode();
> > }
> > catch(Exception e)
> > {
> > System.out.println("Error in Transformation of DOM Document to Sax
Document " + e);
> > }
> >
> 234d260
> <
> 248,253c274,279
> < catch (SAXException e)
> < {
> < throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> < "Parsing error, response was:\n"
+e.getMessage(),
> < e);
> < }
> ---
> > // catch (SAXException e)
> > // {
> > // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> > // "Parsing error, response was:\n"
+e.getMessage(),
> > // e);
> > // }
> diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
/home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
> 70c70
> < private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> ---
> > private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
> 106d105
> <
> 249a249
> >
> 252,255c252
> < Element tempEl = (Element) tempNode;
> < String namespaceURI = (prefix == null)
> < ? getAttribute (tempEl, "xmlns")
> < : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> ---
> > Element tempEl = (Element) tempNode;
> 257,264c254,276
> < if (namespaceURI != null)
> < {
> < return namespaceURI;
> < }
> < else
> < {
> < tempNode = tempEl.getParentNode ();
> < }
> ---
> > String namespaceURI ;
> >
> > try
> > {
> > namespaceURI = (prefix == null)
> > ? getAttribute (tempEl, "xmlns")
> > : getAttributeNS (tempEl, NS_URI_XMLNS,
prefix);
> > }
> > // Raj Yellapragada Here I am checking for NullPointerException and if
it is I am using
> > // Element getattribute method to get to namespaceURI.
> > catch(java.lang.NullPointerException e)
> > {
> > namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> > }
> > if (namespaceURI != null)
> > {
> >
> > return namespaceURI;
> > }
> > else
> > {
> > tempNode = tempEl.getParentNode ();
> > }
> 266c278
> <
> ---
> >
>
>
> Scott Nichol <sc...@yahoo.com> wrote: Raj,
>
> Are you still interested in contributing this code?
>
> Scott Nichol
>
> --- yellapragada rajasekhar wrote:
> >
> > Hi ,
> >
> > My Name is Raj . I work for Insurance Company in
> > Scottsdale. Recently
> > my company asked me to look into web services. I
> > started downloading
> > SOAP stuff from apache site, I wrote small programs
> > every thing works
> > great. But when I really started doing prototype of
> > an existing application
> > , it doesn't seem to be working right. Like if Data
> > over the wire from
> > Database to Tomcat/SOAP server to Browser is minimal
> > then it
> > takes few seconds to process, but if data is huge (>
> > 300 Kb) then it really
> > slows down. Then I started digging into your code, I
> > found couple of
> > things I can change like you guys are using DOM
> > Parser which is Memory
> > intensive , So started changing your code to use
> > SAXParser and also I need
> > to changing couple of things in your DOMUtils code
> > too. So now it works
> > very fast like in seconds I can see output. So I
> > would like share my
> > code and see what you guys think , also wants to
> > contribute to
> > development. Not sure how to proceed can some body
> > help me on this...
> >
> >
> >
> > Thanks,
> > Raj
> >
> >
> >
> >
> >
> > Raja Sekhar.Y
> Software Eng.
>
> >
> >
> > ---------------------------------
> > Do You Yahoo!?
> > LAUNCH - Your Yahoo! Music Experience
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! - Official partner of 2002 FIFA World Cup
> http://fifaworldcup.yahoo.com
>
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> New! SBC Yahoo! Dial - 1st Month Free & unlimited access--
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> Yahoo! Autos - Get free new car price quotes
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Scott,
Please let me know the status on this one .
Thanks,
Raj.
yellapragada rajasekhar <ra...@yahoo.com> wrote:
Scott,
Sorry It took so long to reply. Anyway I have generated patch for two files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils, these files are attached to the mail. And here is the patch file
diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
76a77,84
> import javax.xml.transform.dom.DOMResult; // JAXP
> import javax.xml.transform.sax.SAXSource; // JAXP
> import javax.xml.transform.TransformerFactory; // JAXP
> import javax.xml.transform.Transformer; // JAXP
> import javax.xml.transform.dom.DOMSource; // JAXP
> import javax.xml.transform.stream.StreamResult; // JAXP
>
>
215,216c223,243
< Document respDoc =
< xdb.parse(new InputSource(new StringReader(payloadStr)));
---
> Document respDoc = null;
> // author Raj Yellapragada
> // Here I have generated SAX document instead of DOM document using Transformation functions in
> // JAXP tools. This is way faster than DOM parser (xdb).
> // Document respDoc =
> // xdb.parse(new InputSource(new StringReader(payloadStr)));
> // Document document = null;
> try
> {
>
> DOMResult output = new DOMResult();
> TransformerFactory xformFactory = TransformerFactory.newInstance();
> Transformer idTransform = xformFactory.newTransformer();
> idTransform.transform(new SAXSource(new InputSource(new StringReader(payloadStr))), output);
> respDoc = (Document) output.getNode();
> }
> catch(Exception e)
> {
> System.out.println("Error in Transformation of DOM Document to Sax Document " + e);
> }
>
234d260
<
248,253c274,279
< catch (SAXException e)
< {
< throw new SOAPException(Constants.FAULT_CODE_CLIENT,
< "Parsing error, response was:\n" +e.getMessage(),
< e);
< }
---
> // catch (SAXException e)
> // {
> // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> // "Parsing error, response was:\n" +e.getMessage(),
> // e);
> // }
diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
70c70
< private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
---
> private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
106d105
<
249a249
>
252,255c252
< Element tempEl = (Element) tempNode;
< String namespaceURI = (prefix == null)
< ? getAttribute (tempEl, "xmlns")
< : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
---
> Element tempEl = (Element) tempNode;
257,264c254,276
< if (namespaceURI != null)
< {
< return namespaceURI;
< }
< else
< {
< tempNode = tempEl.getParentNode ();
< }
---
> String namespaceURI ;
>
> try
> {
> namespaceURI = (prefix == null)
> ? getAttribute (tempEl, "xmlns")
> : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
> }
> // Raj Yellapragada Here I am checking for NullPointerException and if it is I am using
> // Element getattribute method to get to namespaceURI.
> catch(java.lang.NullPointerException e)
> {
> namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> }
> if (namespaceURI != null)
> {
>
> return namespaceURI;
> }
> else
> {
> tempNode = tempEl.getParentNode ();
> }
266c278
<
---
>
Scott Nichol <sc...@yahoo.com> wrote: Raj,
Are you still interested in contributing this code?
Scott Nichol
--- yellapragada rajasekhar wrote:
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in
> Scottsdale. Recently
> my company asked me to look into web services. I
> started downloading
> SOAP stuff from apache site, I wrote small programs
> every thing works
> great. But when I really started doing prototype of
> an existing application
> , it doesn't seem to be working right. Like if Data
> over the wire from
> Database to Tomcat/SOAP server to Browser is minimal
> then it
> takes few seconds to process, but if data is huge (>
> 300 Kb) then it really
> slows down. Then I started digging into your code, I
> found couple of
> things I can change like you guys are using DOM
> Parser which is Memory
> intensive , So started changing your code to use
> SAXParser and also I need
> to changing couple of things in your DOMUtils code
> too. So now it works
> very fast like in seconds I can see output. So I
> would like share my
> code and see what you guys think , also wants to
> contribute to
> development. Not sure how to proceed can some body
> help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y
Software Eng.
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
New! SBC Yahoo! Dial - 1st Month Free & unlimited access--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Scott,
Please let me know the status on this one .
Thanks,
Raj.
yellapragada rajasekhar <ra...@yahoo.com> wrote:
Scott,
Sorry It took so long to reply. Anyway I have generated patch for two files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils, these files are attached to the mail. And here is the patch file
diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
76a77,84
> import javax.xml.transform.dom.DOMResult; // JAXP
> import javax.xml.transform.sax.SAXSource; // JAXP
> import javax.xml.transform.TransformerFactory; // JAXP
> import javax.xml.transform.Transformer; // JAXP
> import javax.xml.transform.dom.DOMSource; // JAXP
> import javax.xml.transform.stream.StreamResult; // JAXP
>
>
215,216c223,243
< Document respDoc =
< xdb.parse(new InputSource(new StringReader(payloadStr)));
---
> Document respDoc = null;
> // author Raj Yellapragada
> // Here I have generated SAX document instead of DOM document using Transformation functions in
> // JAXP tools. This is way faster than DOM parser (xdb).
> // Document respDoc =
> // xdb.parse(new InputSource(new StringReader(payloadStr)));
> // Document document = null;
> try
> {
>
> DOMResult output = new DOMResult();
> TransformerFactory xformFactory = TransformerFactory.newInstance();
> Transformer idTransform = xformFactory.newTransformer();
> idTransform.transform(new SAXSource(new InputSource(new StringReader(payloadStr))), output);
> respDoc = (Document) output.getNode();
> }
> catch(Exception e)
> {
> System.out.println("Error in Transformation of DOM Document to Sax Document " + e);
> }
>
234d260
<
248,253c274,279
< catch (SAXException e)
< {
< throw new SOAPException(Constants.FAULT_CODE_CLIENT,
< "Parsing error, response was:\n" +e.getMessage(),
< e);
< }
---
> // catch (SAXException e)
> // {
> // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> // "Parsing error, response was:\n" +e.getMessage(),
> // e);
> // }
diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
70c70
< private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
---
> private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
106d105
<
249a249
>
252,255c252
< Element tempEl = (Element) tempNode;
< String namespaceURI = (prefix == null)
< ? getAttribute (tempEl, "xmlns")
< : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
---
> Element tempEl = (Element) tempNode;
257,264c254,276
< if (namespaceURI != null)
< {
< return namespaceURI;
< }
< else
< {
< tempNode = tempEl.getParentNode ();
< }
---
> String namespaceURI ;
>
> try
> {
> namespaceURI = (prefix == null)
> ? getAttribute (tempEl, "xmlns")
> : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
> }
> // Raj Yellapragada Here I am checking for NullPointerException and if it is I am using
> // Element getattribute method to get to namespaceURI.
> catch(java.lang.NullPointerException e)
> {
> namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> }
> if (namespaceURI != null)
> {
>
> return namespaceURI;
> }
> else
> {
> tempNode = tempEl.getParentNode ();
> }
266c278
<
---
>
Scott Nichol <sc...@yahoo.com> wrote: Raj,
Are you still interested in contributing this code?
Scott Nichol
--- yellapragada rajasekhar wrote:
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in
> Scottsdale. Recently
> my company asked me to look into web services. I
> started downloading
> SOAP stuff from apache site, I wrote small programs
> every thing works
> great. But when I really started doing prototype of
> an existing application
> , it doesn't seem to be working right. Like if Data
> over the wire from
> Database to Tomcat/SOAP server to Browser is minimal
> then it
> takes few seconds to process, but if data is huge (>
> 300 Kb) then it really
> slows down. Then I started digging into your code, I
> found couple of
> things I can change like you guys are using DOM
> Parser which is Memory
> intensive , So started changing your code to use
> SAXParser and also I need
> to changing couple of things in your DOMUtils code
> too. So now it works
> very fast like in seconds I can see output. So I
> would like share my
> code and see what you guys think , also wants to
> contribute to
> development. Not sure how to proceed can some body
> help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y
Software Eng.
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
New! SBC Yahoo! Dial - 1st Month Free & unlimited access--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Scott,
Sorry It took so long to reply. Anyway I have generated patch for two files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils, these files are attached to the mail. And here is the patch file
diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
76a77,84
> import javax.xml.transform.dom.DOMResult; // JAXP
> import javax.xml.transform.sax.SAXSource; // JAXP
> import javax.xml.transform.TransformerFactory; // JAXP
> import javax.xml.transform.Transformer; // JAXP
> import javax.xml.transform.dom.DOMSource; // JAXP
> import javax.xml.transform.stream.StreamResult; // JAXP
>
>
215,216c223,243
< Document respDoc =
< xdb.parse(new InputSource(new StringReader(payloadStr)));
---
> Document respDoc = null;
> // author Raj Yellapragada
> // Here I have generated SAX document instead of DOM document using Transformation functions in
> // JAXP tools. This is way faster than DOM parser (xdb).
> // Document respDoc =
> // xdb.parse(new InputSource(new StringReader(payloadStr)));
> // Document document = null;
> try
> {
>
> DOMResult output = new DOMResult();
> TransformerFactory xformFactory = TransformerFactory.newInstance();
> Transformer idTransform = xformFactory.newTransformer();
> idTransform.transform(new SAXSource(new InputSource(new StringReader(payloadStr))), output);
> respDoc = (Document) output.getNode();
> }
> catch(Exception e)
> {
> System.out.println("Error in Transformation of DOM Document to Sax Document " + e);
> }
>
234d260
<
248,253c274,279
< catch (SAXException e)
< {
< throw new SOAPException(Constants.FAULT_CODE_CLIENT,
< "Parsing error, response was:\n" +e.getMessage(),
< e);
< }
---
> // catch (SAXException e)
> // {
> // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> // "Parsing error, response was:\n" +e.getMessage(),
> // e);
> // }
diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
70c70
< private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
---
> private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
106d105
<
249a249
>
252,255c252
< Element tempEl = (Element) tempNode;
< String namespaceURI = (prefix == null)
< ? getAttribute (tempEl, "xmlns")
< : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
---
> Element tempEl = (Element) tempNode;
257,264c254,276
< if (namespaceURI != null)
< {
< return namespaceURI;
< }
< else
< {
< tempNode = tempEl.getParentNode ();
< }
---
> String namespaceURI ;
>
> try
> {
> namespaceURI = (prefix == null)
> ? getAttribute (tempEl, "xmlns")
> : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
> }
> // Raj Yellapragada Here I am checking for NullPointerException and if it is I am using
> // Element getattribute method to get to namespaceURI.
> catch(java.lang.NullPointerException e)
> {
> namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> }
> if (namespaceURI != null)
> {
>
> return namespaceURI;
> }
> else
> {
> tempNode = tempEl.getParentNode ();
> }
266c278
<
---
>
Scott Nichol <sc...@yahoo.com> wrote: Raj,
Are you still interested in contributing this code?
Scott Nichol
--- yellapragada rajasekhar wrote:
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in
> Scottsdale. Recently
> my company asked me to look into web services. I
> started downloading
> SOAP stuff from apache site, I wrote small programs
> every thing works
> great. But when I really started doing prototype of
> an existing application
> , it doesn't seem to be working right. Like if Data
> over the wire from
> Database to Tomcat/SOAP server to Browser is minimal
> then it
> takes few seconds to process, but if data is huge (>
> 300 Kb) then it really
> slows down. Then I started digging into your code, I
> found couple of
> things I can change like you guys are using DOM
> Parser which is Memory
> intensive , So started changing your code to use
> SAXParser and also I need
> to changing couple of things in your DOMUtils code
> too. So now it works
> very fast like in seconds I can see output. So I
> would like share my
> code and see what you guys think , also wants to
> contribute to
> development. Not sure how to proceed can some body
> help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y
Software Eng.
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
New! SBC Yahoo! Dial - 1st Month Free & unlimited access
Re: [PATCH]Changes to Apache SOAP 2.2 (SAXParser)
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Scott,
Sorry It took so long to reply. Anyway I have generated patch for two files org.apache.soap.rpc.Call and org.apache.soap.util.xml.DOMUtils, these files are attached to the mail. And here is the patch file
diff -r xml-soap/java/src/org/apache/soap/rpc/Call.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/rpc/Call.java
76a77,84
> import javax.xml.transform.dom.DOMResult; // JAXP
> import javax.xml.transform.sax.SAXSource; // JAXP
> import javax.xml.transform.TransformerFactory; // JAXP
> import javax.xml.transform.Transformer; // JAXP
> import javax.xml.transform.dom.DOMSource; // JAXP
> import javax.xml.transform.stream.StreamResult; // JAXP
>
>
215,216c223,243
< Document respDoc =
< xdb.parse(new InputSource(new StringReader(payloadStr)));
---
> Document respDoc = null;
> // author Raj Yellapragada
> // Here I have generated SAX document instead of DOM document using Transformation functions in
> // JAXP tools. This is way faster than DOM parser (xdb).
> // Document respDoc =
> // xdb.parse(new InputSource(new StringReader(payloadStr)));
> // Document document = null;
> try
> {
>
> DOMResult output = new DOMResult();
> TransformerFactory xformFactory = TransformerFactory.newInstance();
> Transformer idTransform = xformFactory.newTransformer();
> idTransform.transform(new SAXSource(new InputSource(new StringReader(payloadStr))), output);
> respDoc = (Document) output.getNode();
> }
> catch(Exception e)
> {
> System.out.println("Error in Transformation of DOM Document to Sax Document " + e);
> }
>
234d260
<
248,253c274,279
< catch (SAXException e)
< {
< throw new SOAPException(Constants.FAULT_CODE_CLIENT,
< "Parsing error, response was:\n" +e.getMessage(),
< e);
< }
---
> // catch (SAXException e)
> // {
> // throw new SOAPException(Constants.FAULT_CODE_CLIENT,
> // "Parsing error, response was:\n" +e.getMessage(),
> // e);
> // }
diff -r xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java /home/rgc/rajfix/xml-soap/java/src/org/apache/soap/util/xml/DOMUtils.java
70c70
< private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
---
> private static String NS_URI_XMLNS = "http://www.w3.org/2000/xmlns/";
106d105
<
249a249
>
252,255c252
< Element tempEl = (Element) tempNode;
< String namespaceURI = (prefix == null)
< ? getAttribute (tempEl, "xmlns")
< : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
---
> Element tempEl = (Element) tempNode;
257,264c254,276
< if (namespaceURI != null)
< {
< return namespaceURI;
< }
< else
< {
< tempNode = tempEl.getParentNode ();
< }
---
> String namespaceURI ;
>
> try
> {
> namespaceURI = (prefix == null)
> ? getAttribute (tempEl, "xmlns")
> : getAttributeNS (tempEl, NS_URI_XMLNS, prefix);
> }
> // Raj Yellapragada Here I am checking for NullPointerException and if it is I am using
> // Element getattribute method to get to namespaceURI.
> catch(java.lang.NullPointerException e)
> {
> namespaceURI = tempEl.getAttribute("xmlns:" + prefix);
> }
> if (namespaceURI != null)
> {
>
> return namespaceURI;
> }
> else
> {
> tempNode = tempEl.getParentNode ();
> }
266c278
<
---
>
Scott Nichol <sc...@yahoo.com> wrote: Raj,
Are you still interested in contributing this code?
Scott Nichol
--- yellapragada rajasekhar wrote:
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in
> Scottsdale. Recently
> my company asked me to look into web services. I
> started downloading
> SOAP stuff from apache site, I wrote small programs
> every thing works
> great. But when I really started doing prototype of
> an existing application
> , it doesn't seem to be working right. Like if Data
> over the wire from
> Database to Tomcat/SOAP server to Browser is minimal
> then it
> takes few seconds to process, but if data is huge (>
> 300 Kb) then it really
> slows down. Then I started digging into your code, I
> found couple of
> things I can change like you guys are using DOM
> Parser which is Memory
> intensive , So started changing your code to use
> SAXParser and also I need
> to changing couple of things in your DOMUtils code
> too. So now it works
> very fast like in seconds I can see output. So I
> would like share my
> code and see what you guys think , also wants to
> contribute to
> development. Not sure how to proceed can some body
> help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y
Software Eng.
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail:
For additional commands, e-mail:
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
New! SBC Yahoo! Dial - 1st Month Free & unlimited access
Re: Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sc...@yahoo.com>.
Raj,
Are you still interested in contributing this code?
Scott Nichol
--- yellapragada rajasekhar <ra...@yahoo.com> wrote:
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in
> Scottsdale. Recently
> my company asked me to look into web services. I
> started downloading
> SOAP stuff from apache site, I wrote small programs
> every thing works
> great. But when I really started doing prototype of
> an existing application
> , it doesn't seem to be working right. Like if Data
> over the wire from
> Database to Tomcat/SOAP server to Browser is minimal
> then it
> takes few seconds to process, but if data is huge (>
> 300 Kb) then it really
> slows down. Then I started digging into your code, I
> found couple of
> things I can change like you guys are using DOM
> Parser which is Memory
> intensive , So started changing your code to use
> SAXParser and also I need
> to changing couple of things in your DOMUtils code
> too. So now it works
> very fast like in seconds I can see output. So I
> would like share my
> code and see what you guys think , also wants to
> contribute to
> development. Not sure how to proceed can some body
> help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: Changes to Apache SOAP 2.2 (SAXParser)
Posted by Scott Nichol <sc...@yahoo.com>.
Raj,
Are you still interested in contributing this code?
Scott Nichol
--- yellapragada rajasekhar <ra...@yahoo.com> wrote:
>
> Hi ,
>
> My Name is Raj . I work for Insurance Company in
> Scottsdale. Recently
> my company asked me to look into web services. I
> started downloading
> SOAP stuff from apache site, I wrote small programs
> every thing works
> great. But when I really started doing prototype of
> an existing application
> , it doesn't seem to be working right. Like if Data
> over the wire from
> Database to Tomcat/SOAP server to Browser is minimal
> then it
> takes few seconds to process, but if data is huge (>
> 300 Kb) then it really
> slows down. Then I started digging into your code, I
> found couple of
> things I can change like you guys are using DOM
> Parser which is Memory
> intensive , So started changing your code to use
> SAXParser and also I need
> to changing couple of things in your DOMUtils code
> too. So now it works
> very fast like in seconds I can see output. So I
> would like share my
> code and see what you guys think , also wants to
> contribute to
> development. Not sure how to proceed can some body
> help me on this...
>
>
>
> Thanks,
> Raj
>
>
>
>
>
> Raja Sekhar.Y<BR>Software Eng.<BR>
>
>
> ---------------------------------
> Do You Yahoo!?
> LAUNCH - Your Yahoo! Music Experience
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
Re: Changes to Apache SOAP 2.2
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Hi ,
My Name is Raj . I work for Insurance Company in Scottsdale. Recently
my company asked me to look into web services. I started downloading
SOAP stuff from apache site, I wrote small programs every thing works
great. But when I really started doing prototype of an existing application
, it doesn't seem to be working right. Like if Data over the wire from
Database to Tomcat/SOAP server to Browser is minimal then it
takes few seconds to process, but if data is huge (> 300 Kb) then it really
slows down. Then I started digging into your code, I found couple of
things I can change like you guys are using DOM Parser which is Memory
intensive , So started changing your code to use SAXParser and also I need
to changing couple of things in your DOMUtils code too. So now it works
very fast like in seconds I can see output. So I would like share my
code and see what you guys think , also wants to contribute to
development. Not sure how to proceed can some body help me on this...
Thanks,
Raj
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
Re: Changes to Apache SOAP 2.2
Posted by yellapragada rajasekhar <ra...@yahoo.com>.
Hi ,
My Name is Raj . I work for Insurance Company in Scottsdale. Recently
my company asked me to look into web services. I started downloading
SOAP stuff from apache site, I wrote small programs every thing works
great. But when I really started doing prototype of an existing application
, it doesn't seem to be working right. Like if Data over the wire from
Database to Tomcat/SOAP server to Browser is minimal then it
takes few seconds to process, but if data is huge (> 300 Kb) then it really
slows down. Then I started digging into your code, I found couple of
things I can change like you guys are using DOM Parser which is Memory
intensive , So started changing your code to use SAXParser and also I need
to changing couple of things in your DOMUtils code too. So now it works
very fast like in seconds I can see output. So I would like share my
code and see what you guys think , also wants to contribute to
development. Not sure how to proceed can some body help me on this...
Thanks,
Raj
Raja Sekhar.Y<BR>Software Eng.<BR>
---------------------------------
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
Re: Vote: Apache SOAP 2.3 Release Schedule
Posted by "William A. Nagy" <na...@watson.ibm.com>.
I was able to completely isolate the change, so I have added it in.
There is now a method on SOAPHTTPConnection which will allow you to
set the value for TcpNoDelay. The default remains whatever your
JVM/socket implementation has chosen it to be. We hope to put RC2 up
either later today or early tomorrow, so the change should be in there.
-Bill
>Dan,
>
>Does the patch you posted always call setTcpNoDelay(true)? I wonder whether it
>is better to give the developer the option of whether to do this or not, e.g. by
>adding methods to SOAPHTTPConnection to get/set whether to disable Nagle, then
>adding another overloaded post method to HTTPUtils that takes a parameter as to
>whether to disable Nagle. The default would be not to disable, so that everyone
>who does not explicitly disable will get the same behavior as they do currently.
>
>Just a thought.
>
>Scott Nichol
>
>----- Original Message -----
>From: "Dan Davis" <da...@caip.rutgers.edu>
>To: <so...@xml.apache.org>
>Sent: Wednesday, May 22, 2002 2:44 AM
>Subject: Re: Vote: Apache SOAP 2.3 Release Schedule
>
>
>>
>> +0
>>
>> I wanted to make sure a change I made to HTTPUtils.java is included.
>> I'm presenting a paper that includes this change. In HTTPUtils.java,
>> call setTcpNoDelay (true) once you've got the socket. This disables
>> the Nagle algorithm on the client side and speeds up each individual
>> client substantially -- 200 ms to 20 ms on a LAN, no effect if both
>> client and server are on the same host.
>>
>> I posted this change earlier, but never made a bug report, so I wasn't
>> sure the change would make it in.
>>
>> I'm sorry I've taken so long to reply to vote, but I'm on vacation and
>> finally got access to the email where I receive soap-dev.
>>
>> I've tested this change in both applet and standalone, as I'd been
>> concerned that setting socket options might violate security restrictions
>> in some browsers/JVM's. I know Sun's is okay, and suspect that all
>> Java 2 JVM's will be fine, but I haven't tried it with a good number
>> of JVMs.
>>
>> ******************************
>> I'm participating this summer in a 150 mile bike-a-thon to end Multiple
>> Sclerosis. If you would like to make a donation to help, please contact me
>> or visit this URL:
>> https://www.nationalmssociety.org/pledge/pledge.asp?participantid=61823
>> to pledge on-line. Thanks!
>> ******************************
>>
>>
>>
Re: Vote: Apache SOAP 2.3 Release Schedule
Posted by "William A. Nagy" <na...@watson.ibm.com>.
I was able to completely isolate the change, so I have added it in.
There is now a method on SOAPHTTPConnection which will allow you to
set the value for TcpNoDelay. The default remains whatever your
JVM/socket implementation has chosen it to be. We hope to put RC2 up
either later today or early tomorrow, so the change should be in there.
-Bill
>Dan,
>
>Does the patch you posted always call setTcpNoDelay(true)? I wonder whether it
>is better to give the developer the option of whether to do this or not, e.g. by
>adding methods to SOAPHTTPConnection to get/set whether to disable Nagle, then
>adding another overloaded post method to HTTPUtils that takes a parameter as to
>whether to disable Nagle. The default would be not to disable, so that everyone
>who does not explicitly disable will get the same behavior as they do currently.
>
>Just a thought.
>
>Scott Nichol
>
>----- Original Message -----
>From: "Dan Davis" <da...@caip.rutgers.edu>
>To: <so...@xml.apache.org>
>Sent: Wednesday, May 22, 2002 2:44 AM
>Subject: Re: Vote: Apache SOAP 2.3 Release Schedule
>
>
>>
>> +0
>>
>> I wanted to make sure a change I made to HTTPUtils.java is included.
>> I'm presenting a paper that includes this change. In HTTPUtils.java,
>> call setTcpNoDelay (true) once you've got the socket. This disables
>> the Nagle algorithm on the client side and speeds up each individual
>> client substantially -- 200 ms to 20 ms on a LAN, no effect if both
>> client and server are on the same host.
>>
>> I posted this change earlier, but never made a bug report, so I wasn't
>> sure the change would make it in.
>>
>> I'm sorry I've taken so long to reply to vote, but I'm on vacation and
>> finally got access to the email where I receive soap-dev.
>>
>> I've tested this change in both applet and standalone, as I'd been
>> concerned that setting socket options might violate security restrictions
>> in some browsers/JVM's. I know Sun's is okay, and suspect that all
>> Java 2 JVM's will be fine, but I haven't tried it with a good number
>> of JVMs.
>>
>> ******************************
>> I'm participating this summer in a 150 mile bike-a-thon to end Multiple
>> Sclerosis. If you would like to make a donation to help, please contact me
>> or visit this URL:
>> https://www.nationalmssociety.org/pledge/pledge.asp?participantid=61823
>> to pledge on-line. Thanks!
>> ******************************
>>
>>
>>
Re: Vote: Apache SOAP 2.3 Release Schedule
Posted by Scott Nichol <sn...@scottnichol.com>.
Dan,
Does the patch you posted always call setTcpNoDelay(true)? I wonder whether it
is better to give the developer the option of whether to do this or not, e.g. by
adding methods to SOAPHTTPConnection to get/set whether to disable Nagle, then
adding another overloaded post method to HTTPUtils that takes a parameter as to
whether to disable Nagle. The default would be not to disable, so that everyone
who does not explicitly disable will get the same behavior as they do currently.
Just a thought.
Scott Nichol
----- Original Message -----
From: "Dan Davis" <da...@caip.rutgers.edu>
To: <so...@xml.apache.org>
Sent: Wednesday, May 22, 2002 2:44 AM
Subject: Re: Vote: Apache SOAP 2.3 Release Schedule
>
> +0
>
> I wanted to make sure a change I made to HTTPUtils.java is included.
> I'm presenting a paper that includes this change. In HTTPUtils.java,
> call setTcpNoDelay (true) once you've got the socket. This disables
> the Nagle algorithm on the client side and speeds up each individual
> client substantially -- 200 ms to 20 ms on a LAN, no effect if both
> client and server are on the same host.
>
> I posted this change earlier, but never made a bug report, so I wasn't
> sure the change would make it in.
>
> I'm sorry I've taken so long to reply to vote, but I'm on vacation and
> finally got access to the email where I receive soap-dev.
>
> I've tested this change in both applet and standalone, as I'd been
> concerned that setting socket options might violate security restrictions
> in some browsers/JVM's. I know Sun's is okay, and suspect that all
> Java 2 JVM's will be fine, but I haven't tried it with a good number
> of JVMs.
>
> ******************************
> I'm participating this summer in a 150 mile bike-a-thon to end Multiple
> Sclerosis. If you would like to make a donation to help, please contact me
> or visit this URL:
> https://www.nationalmssociety.org/pledge/pledge.asp?participantid=61823
> to pledge on-line. Thanks!
> ******************************
>
>
>
Re: Vote: Apache SOAP 2.3 Release Schedule
Posted by Scott Nichol <sn...@scottnichol.com>.
Dan,
Does the patch you posted always call setTcpNoDelay(true)? I wonder whether it
is better to give the developer the option of whether to do this or not, e.g. by
adding methods to SOAPHTTPConnection to get/set whether to disable Nagle, then
adding another overloaded post method to HTTPUtils that takes a parameter as to
whether to disable Nagle. The default would be not to disable, so that everyone
who does not explicitly disable will get the same behavior as they do currently.
Just a thought.
Scott Nichol
----- Original Message -----
From: "Dan Davis" <da...@caip.rutgers.edu>
To: <so...@xml.apache.org>
Sent: Wednesday, May 22, 2002 2:44 AM
Subject: Re: Vote: Apache SOAP 2.3 Release Schedule
>
> +0
>
> I wanted to make sure a change I made to HTTPUtils.java is included.
> I'm presenting a paper that includes this change. In HTTPUtils.java,
> call setTcpNoDelay (true) once you've got the socket. This disables
> the Nagle algorithm on the client side and speeds up each individual
> client substantially -- 200 ms to 20 ms on a LAN, no effect if both
> client and server are on the same host.
>
> I posted this change earlier, but never made a bug report, so I wasn't
> sure the change would make it in.
>
> I'm sorry I've taken so long to reply to vote, but I'm on vacation and
> finally got access to the email where I receive soap-dev.
>
> I've tested this change in both applet and standalone, as I'd been
> concerned that setting socket options might violate security restrictions
> in some browsers/JVM's. I know Sun's is okay, and suspect that all
> Java 2 JVM's will be fine, but I haven't tried it with a good number
> of JVMs.
>
> ******************************
> I'm participating this summer in a 150 mile bike-a-thon to end Multiple
> Sclerosis. If you would like to make a donation to help, please contact me
> or visit this URL:
> https://www.nationalmssociety.org/pledge/pledge.asp?participantid=61823
> to pledge on-line. Thanks!
> ******************************
>
>
>
Re: Vote: Apache SOAP 2.3 Release Schedule
Posted by Dan Davis <da...@caip.rutgers.edu>.
+0
I wanted to make sure a change I made to HTTPUtils.java is included.
I'm presenting a paper that includes this change. In HTTPUtils.java,
call setTcpNoDelay (true) once you've got the socket. This disables
the Nagle algorithm on the client side and speeds up each individual
client substantially -- 200 ms to 20 ms on a LAN, no effect if both
client and server are on the same host.
I posted this change earlier, but never made a bug report, so I wasn't
sure the change would make it in.
I'm sorry I've taken so long to reply to vote, but I'm on vacation and
finally got access to the email where I receive soap-dev.
I've tested this change in both applet and standalone, as I'd been
concerned that setting socket options might violate security restrictions
in some browsers/JVM's. I know Sun's is okay, and suspect that all
Java 2 JVM's will be fine, but I haven't tried it with a good number
of JVMs.
******************************
I'm participating this summer in a 150 mile bike-a-thon to end Multiple
Sclerosis. If you would like to make a donation to help, please contact me
or visit this URL:
https://www.nationalmssociety.org/pledge/pledge.asp?participantid=61823
to pledge on-line. Thanks!
******************************
RE: Vote: Apache SOAP 2.3 Release Schedule
Posted by "Matthew J. Duftler" <du...@watson.ibm.com>.
<ballot>
[X] +1 I approve this plan, and will help
[ ] +0 I approve this plan, but can't help
[ ] -0 I am not in favor of this plan
[ ] -1 I am against this plan, because:
</ballot>
> -----Original Message-----
> From: William A. Nagy [mailto:nagy@watson.ibm.com]
> Sent: Monday, May 13, 2002 4:06 PM
> To: soap-dev@xml.apache.org
> Subject: Vote: Apache SOAP 2.3 Release Schedule
>
>
> I'd like to call for a vote on the Apache SOAP 2.3 Release Plan.
>
> The vote will run until 04/25.
>
> <ballot>
> [ ] +1 I approve this plan, and will help
> [ ] +0 I approve this plan, but can't help
> [ ] -0 I am not in favor of this plan
> [ ] -1 I am against this plan, because:
>
> </ballot>
>
> -Bill
>
>
> Release Plan for Apache SOAP 2.3
> ==================================
>
> Introduction:
> ------------
>
> This document is a release plan for the release of Apache SOAP
> 2.3.
>
> The goal of the Apache SOAP 2.3 release is to capture all of the
> bug-fixes that have been made since v2.2 in a "permanent" build.
>
> This Release Plan proposes the following schedule:
>
> Wednesday, May 15, 2002 Apache SOAP 2.3 Beta 1
>
> Wednesday, May 22, 2002 Apache SOAP 2.3 Release Candidate
>
> Friday, May 24, 2002 Apache SOAP 2.3 Release
>
> This is an aggressive schedule, but no significant functionality has
> been added since 2.2 and most people are already using the nightly
> builds.
>
> After the first 2.3 Release Candidate, other RC releases may be made
> as needed until one is promoted as Final by the SOAP committers.
>
> If you discover any outstanding bugs, please post them to Bugzilla.
>
>
>
>
Re: Vote: Apache SOAP 2.3 Release Schedule
Posted by Dan Davis <da...@caip.rutgers.edu>.
+0
I wanted to make sure a change I made to HTTPUtils.java is included.
I'm presenting a paper that includes this change. In HTTPUtils.java,
call setTcpNoDelay (true) once you've got the socket. This disables
the Nagle algorithm on the client side and speeds up each individual
client substantially -- 200 ms to 20 ms on a LAN, no effect if both
client and server are on the same host.
I posted this change earlier, but never made a bug report, so I wasn't
sure the change would make it in.
I'm sorry I've taken so long to reply to vote, but I'm on vacation and
finally got access to the email where I receive soap-dev.
I've tested this change in both applet and standalone, as I'd been
concerned that setting socket options might violate security restrictions
in some browsers/JVM's. I know Sun's is okay, and suspect that all
Java 2 JVM's will be fine, but I haven't tried it with a good number
of JVMs.
******************************
I'm participating this summer in a 150 mile bike-a-thon to end Multiple
Sclerosis. If you would like to make a donation to help, please contact me
or visit this URL:
https://www.nationalmssociety.org/pledge/pledge.asp?participantid=61823
to pledge on-line. Thanks!
******************************