[jira] Created: (SOAP-165) Exceptions from deserializer not sent by faultListener

2004-03-17 Thread jira
Message: A new issue has been created in JIRA. - View the issue: http://issues.apache.org/jira/secure/ViewIssue.jspa?key=SOAP-165 Here is an overview of the issue:

[jira] Assigned: (SOAP-165) Exceptions from deserializer not sent by faultListener

2004-03-17 Thread jira
Message: The following issue has been re-assigned. Assignee: Scott Nichol (mailto:[EMAIL PROTECTED]) - View the issue: http://issues.apache.org/jira/secure/ViewIssue.jspa?key=SOAP-165 Here is an overview of the issue: --

[jira] Commented: (SOAP-165) Exceptions from deserializer not sent by faultListener

2004-03-17 Thread jira
The following comment has been added to this issue: Author: Scott Nichol Created: Wed, 17 Mar 2004 7:30 AM Body: Christian - can you attach your patch? A "diff -u" is the preferred format. - View this comment:

[jira] Updated: (SOAP-165) Exceptions from deserializer not sent by faultListener

2004-03-17 Thread jira
The following issue has been updated: Updater: Christian Landbo (mailto:[EMAIL PROTECTED]) Date: Wed, 17 Mar 2004 8:40 AM Comment: Sorry it is not in 'diff -u' format. Changes: Attachment changed to changes.txt ---

retained collectible memory

2004-03-17 Thread WJCarpenter
I've been fooling around looking at how much free memory is left after making SOAP calls, and I think there is a problem in the DocumentBuilder pool, but I'm not sure what to do about it (or if anything can or should be done about it). In a nutshell, I observe that there is some chunk of memory he