[
https://issues.apache.org/jira/browse/TUSCANY-1814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532782
]
Raymond Feng commented on TUSCANY-1814:
---------------------------------------
Thank you for the test case and it helps. I checked in the fix under r582399. I
can start your composite successfully.
Back to the memory consumption, worth to point out that Apache XmlSchema
doesn't provide the extensibility to resolve the XSD import/include to another
XmlSchema object. Instead, the imported/included schemas have to be loaded from
the main XSD.
> 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
> Assignee: Raymond Feng
> Fix For: Java-SCA-Next
>
> Attachments: ExampleService.war, Memory Footprint (Startup
> Profile).png, trninq.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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
