Re: [jira] Closed: (SOAP-157) s

2004-04-09 Thread Scott Nichol
Send an e-mail to [EMAIL PROTECTED] Scott Nichol Do not send e-mail directly to this e-mail address, because it is filtered to accept only mail from specific mail lists. - Original Message - From: "GARSKOF, ROBERT D (SNETCOMM)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, A

RE: [jira] Closed: (SOAP-157) s

2004-04-09 Thread GARSKOF, ROBERT D (SNETCOMM)
Please delete me from this list Thanks. -- garskof -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 9:25 AM To: [EMAIL PROTECTED] Subject: [jira] Closed: (SOAP-157) s Message: The following issue has been closed. Resolver: Scott

RE: [jira] Assigned: (SOAP-156) BeanSerializer : bug for indexed properties

2004-04-09 Thread Kerrigan, Grahame
Please remove me from this e-mail list. Thank you. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 09 April 2004 14:35 To: [EMAIL PROTECTED] Subject: [jira] Assigned: (SOAP-156) BeanSerializer : bug for indexed properties Message: The following issue has b

[jira] Assigned: (SOAP-156) BeanSerializer : bug for indexed properties

2004-04-09 Thread jira
Message: The following issue has been re-assigned. Assignee: Scott Nichol (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/browse/SOAP-156 Here is an overview of the issue: -

[jira] Commented: (SOAP-158) SAX parsing error

2004-04-09 Thread jira
The following comment has been added to this issue: Author: Scott Nichol Created: Fri, 9 Apr 2004 6:31 AM Body: Is Complex serialized with BeanSerializer, or a custom Serializer? If the marshall method does a pushScope without a popScope, the observed behavior would occur. -

[jira] Commented: (SOAP-158) SAX parsing error

2004-04-09 Thread jira
The following comment has been added to this issue: Author: Scott Nichol Created: Fri, 9 Apr 2004 6:29 AM Body: This looks like the namespace ns6 gets pushed onto the namespace stack, but does not getting properly popped. ---

[jira] Commented: (SOAP-158) SAX parsing error

2004-04-09 Thread jira
The following comment has been added to this issue: Author: Scott Nichol Created: Fri, 9 Apr 2004 6:28 AM Body: Are you still having this error? If so, is it only using the 2.3.1 release, or does the problem still exist with a nightly build? --

[jira] Assigned: (SOAP-158) SAX parsing error

2004-04-09 Thread jira
Message: The following issue has been re-assigned. Assignee: Scott Nichol (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/browse/SOAP-158 Here is an overview of the issue: -

[jira] Commented: (SOAP-117) Error: 500 :Location: /apache-soap/admin/list.jsp Internal Servlet Error:

2004-04-09 Thread jira
The following comment has been added to this issue: Author: Scott Nichol Created: Fri, 9 Apr 2004 6:25 AM Body: I will ask again and close the issue if there is no response within 24 hours. Are you still having this problem? Do other JSP pages work? --

[jira] Closed: (SOAP-157) s

2004-04-09 Thread jira
Message: The following issue has been closed. Resolver: Scott Nichol Date: Fri, 9 Apr 2004 6:22 AM There is no action to take, as there is no description of a problem. - View the issue: http://issues.apache.org/ji

[jira] Assigned: (SOAP-157) s

2004-04-09 Thread jira
Message: The following issue has been re-assigned. Assignee: Scott Nichol (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/browse/SOAP-157 Here is an overview of the issue: -

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

2004-04-09 Thread snichol
snichol 2004/04/09 06:19:04 Modified:java/samples/doclit GetQuote.java java/src/org/apache/soap/util/net HTTPUtils.java Log: Always clean up socket resources. Revision ChangesPath 1.3 +1 -0 ws-soap/java/samples/doclit/GetQuote.java Index: Ge

[jira] Closed: (SOAP-161) Apache SOAP 2.3.1 socket leak.

2004-04-09 Thread jira
Message: The following issue has been closed. Resolver: Scott Nichol Date: Fri, 9 Apr 2004 6:19 AM Since I never manage to solicit the posting of a patch, I have added a try/finally in HTTPUtils#post. - View the is

[jira] Assigned: (SOAP-161) Apache SOAP 2.3.1 socket leak.

2004-04-09 Thread jira
Message: The following issue has been re-assigned. Assignee: Scott Nichol (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/browse/SOAP-161 Here is an overview of the issue: -

[jira] Commented: (SOAP-145) Version information in MANIFEST.MF file.

2004-04-09 Thread jira
The following comment has been added to this issue: Author: Rick Kellogg Created: Fri, 9 Apr 2004 5:29 AM Body: Thank you. We will all thank you two years from now when we cannot figure out which version we have in production. -

[jira] Closed: (SOAP-145) Version information in MANIFEST.MF file.

2004-04-09 Thread jira
Message: The following issue has been closed. Resolver: Scott Nichol Date: Fri, 9 Apr 2004 5:26 AM This has been changed in build.xml, with both soap.jar and soap.war having manifest that includes the version with a timestamp. ---

[jira] Assigned: (SOAP-145) Version information in MANIFEST.MF file.

2004-04-09 Thread jira
Message: The following issue has been re-assigned. Assignee: Scott Nichol (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/browse/SOAP-145 Here is an overview of the issue: -

[jira] Closed: (SOAP-167) wish soap.jar were built with debug symbols by default

2004-04-09 Thread jira
Message: The following issue has been closed. Resolver: Scott Nichol Date: Fri, 9 Apr 2004 5:19 AM Seems like a good idea. It is what Axis does. I have changed build.xml to have javac debug="on" by default. - Vi

[jira] Assigned: (SOAP-167) wish soap.jar were built with debug symbols by default

2004-04-09 Thread jira
Message: The following issue has been re-assigned. Assignee: Scott Nichol (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/browse/SOAP-167 Here is an overview of the issue: -