[jbossws-issues] [JBoss JIRA] Created: (JBWS-2638) Insufficient optimisation in JBossXSModel traversing XML schema
Darran Lofthouse (JIRA)
jira-events at lists.jboss.org
Fri May 1 10:27:47 EDT 2009
Insufficient optimisation in JBossXSModel traversing XML schema
---------------------------------------------------------------
Key: JBWS-2638
URL: https://jira.jboss.org/jira/browse/JBWS-2638
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.1.1
Reporter: Darran Lofthouse
Assignee: Darran Lofthouse
Fix For: jbossws-native-3.1.2
The JBossXSModel implementation requires further optimisation to reduce deployment overhead for complex schemas.
Take the following type: -
<xs:complexType abstract='true' name='cmisBaseType'>
<xs:sequence>
<xs:choice maxOccurs='unbounded' minOccurs='0'>
<xs:element ref='tns:base'/>
<xs:element ref='tns:baseDateTime'/>
<xs:element ref='tns:baseBoolean'/>
<xs:element ref='tns:baseHtml'/>
<xs:element ref='tns:baseInteger'/>
<xs:element ref='tns:baseDecimal'/>
<xs:element ref='tns:baseString'/>
<xs:element ref='tns:baseId'/>
<xs:element ref='tns:baseUri'/>
<xs:element ref='tns:baseXml'/>
</xs:choice>
</xs:sequence>
</xs:complexType>
If each of the element types referenced here extend this type then there are many routes to reach each type. The class JBossXSModel does detect cyclic references but it does not detect if a type has already been processed if re-visit in a non cyclic way.
This Jira issue it to modify the current optimisation to detect second visits to a type by any route.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossws-issues
mailing list