You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Mike Rheinheimer (JIRA)" <ji...@apache.org> on 2008/09/25 18:09:46 UTC
[jira] Created: (WSCOMMONS-391) allow caching of XmlSchema objects
to speed application loading
allow caching of XmlSchema objects to speed application loading
---------------------------------------------------------------
Key: WSCOMMONS-391
URL: https://issues.apache.org/jira/browse/WSCOMMONS-391
Project: WS-Commons
Issue Type: Improvement
Components: XmlSchema
Reporter: Mike Rheinheimer
If an application has several webservices, each of which has a WSDL, and each of those imports many of the same .xsd schemas, we unnecessarily re-read and re-load the same schemas. We can allow caching in the SchemaBuilder. However, users of the cache must clear it when they're done, and ensure that no runtime modification of the schema or thread-shared reading of the schema occurs.
Will attach patch and commit code shortly. Enhancement does NOT change default behavior in SchemaBuilder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WSCOMMONS-391) allow caching of XmlSchema objects
to speed application loading
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer resolved WSCOMMONS-391.
----------------------------------------
Resolution: Fixed
Committed in 699014
> allow caching of XmlSchema objects to speed application loading
> ---------------------------------------------------------------
>
> Key: WSCOMMONS-391
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-391
> Project: WS-Commons
> Issue Type: Improvement
> Components: XmlSchema
> Reporter: Mike Rheinheimer
> Attachments: patch.txt
>
>
> If an application has several webservices, each of which has a WSDL, and each of those imports many of the same .xsd schemas, we unnecessarily re-read and re-load the same schemas. We can allow caching in the SchemaBuilder. However, users of the cache must clear it when they're done, and ensure that no runtime modification of the schema or thread-shared reading of the schema occurs.
> Will attach patch and commit code shortly. Enhancement does NOT change default behavior in SchemaBuilder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WSCOMMONS-391) allow caching of XmlSchema objects
to speed application loading
Posted by "Mike Rheinheimer (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Rheinheimer updated WSCOMMONS-391:
---------------------------------------
Attachment: patch.txt
> allow caching of XmlSchema objects to speed application loading
> ---------------------------------------------------------------
>
> Key: WSCOMMONS-391
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-391
> Project: WS-Commons
> Issue Type: Improvement
> Components: XmlSchema
> Reporter: Mike Rheinheimer
> Attachments: patch.txt
>
>
> If an application has several webservices, each of which has a WSDL, and each of those imports many of the same .xsd schemas, we unnecessarily re-read and re-load the same schemas. We can allow caching in the SchemaBuilder. However, users of the cache must clear it when they're done, and ensure that no runtime modification of the schema or thread-shared reading of the schema occurs.
> Will attach patch and commit code shortly. Enhancement does NOT change default behavior in SchemaBuilder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.