You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Sunny Ip (JIRA)" <tu...@ws.apache.org> on 2007/10/03 22:58:50 UTC
[jira] Updated: (TUSCANY-1814) Large memory footprint with large
wsdl/schemas
[ https://issues.apache.org/jira/browse/TUSCANY-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sunny Ip updated TUSCANY-1814:
------------------------------
Attachment: wsdl.zip
Noticed another problem caused by this change. When I have a wsdl that includes an xsd that imports another xsd, the TuscanyServletFilter fails to start (console shows SEVERE: Error filterStart) with this change. Going back to Tuscany 1.0 works fine. I have modified and included a wsdl that has this structure.
> Large memory footprint with large wsdl/schemas
> ----------------------------------------------
>
> Key: TUSCANY-1814
> URL: https://issues.apache.org/jira/browse/TUSCANY-1814
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Data Binding Runtime
> Affects Versions: Java-SCA-1.0
> Environment: Windows/Tomcat
> Reporter: Sunny Ip
> Fix For: Java-SCA-Next
>
> Attachments: Memory Footprint (Startup Profile).png, wsdl.zip, wsdl.zip
>
>
> Creating services and components based on large wsdl/schemas (SDO generation/databinding, ws binding, etc.) results in very high memory footprint. Attaching sample wsdls that make use of the very large schema that we are using.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org