Amila,
Thanks for the comments and the postings to the JIRA.
To answer your question about the WSDL definition wrapper:
The problem is having a solution that will work in all WSDL cases
(including the
here is an another option for this problem.
we keep wsdl4j object structure in memory to show the wsdl file to the user
when they request with ?wsdl.
So if we can display the wsdl file without keeping the wsd4j definition then
there is not need to keep the
wsdl4j object and hence solve the
On 9/19/07, Ann Robinson [EMAIL PROTECTED] wrote:
Hi, all,
This is a re-send of the note with the correct [axis2] prefix in the
subject line.
I have updated the proposed fix for the out-of-memory error that occurs on
the server in some environments, and I would be interested in getting
Thanks Ann.
Let me try to summarize to see if I understand this change:
The new patch is the WSDL Wrapper interface without any implementation.
There are no changes to the loading, unloading or logic.
When WSDL4J completes their reloading implementation, then we can easily
plug in the
Hi, all,
I have updated the proposed fix for the out-of-memory error that occurs on
the server in some environments, and I would be interested in getting some
feedback on the updated proposal.
Some background:
This out-of-memory (OOM) error happens on the server in some
