You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@beehive.apache.org by "daryoush mehrtash (JIRA)" <be...@incubator.apache.org> on 2005/06/14 03:47:50 UTC

[jira] Updated: (BEEHIVE-780) WSM leaks InputStreams at build time

     [ http://issues.apache.org/jira/browse/BEEHIVE-780?page=all ]

daryoush mehrtash updated BEEHIVE-780:
--------------------------------------

    Attachment: streampatch.txt

This is the fix for this bug and also 781.  

The interfaces on the classes have been cleaned up by moving the parsing of the xml document out of the XMLBeanWSDLProcess and Schema classes and updated calling classes.  The WSDL to xmlbean parsing has been moved to the org.apache.beehive.wsm.wsdl.Utilitites class.  Also added two unit tests to verify the WSDL to OM logic.  For the test I am using the current Google and Amazon wsdls.  There is no need to update thse WSDLs as we are not really connecting to the service, rather just using the current version of their wsdl as a test data.  We should add more real wsdls in future.  To add the more wsdls you need to drop the wsdl in either encoded-schmeas or schems in the drt/tests.    The build file would generate all types from the wsdl iles before running the tests.


> WSM leaks InputStreams at build time
> ------------------------------------
>
>          Key: BEEHIVE-780
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-780
>      Project: Beehive
>         Type: Bug
>   Components: Web Services (181)
>     Versions: V1, V1Alpha, V1Beta
>     Reporter: Eddie O'Neil
>     Assignee: daryoush mehrtash
>     Priority: Critical
>      Fix For: TBD
>  Attachments: streampatch.txt
>
> The WSM code base leaks InputStreams in the following locations:
>   AbstractWsdl2AJava
>     generateAnnotatedJavaFromWSDL -- an InputStream is used to construct the BeehiveWsTypeMetadata object and is not closed
>   Utilities
>     findSchemaDocument -- an InputStream is passed to the WSDLParser class and is not closed
>   

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira