You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Robbie Minshall (JIRA)" <tu...@ws.apache.org> on 2006/09/07 19:09:22 UTC
[jira] Created: (TUSCANY-708) Should TypeHelper.define return List
of Types that includes DocumentRootType
Should TypeHelper.define return List of Types that includes DocumentRootType
----------------------------------------------------------------------------
Key: TUSCANY-708
URL: http://issues.apache.org/jira/browse/TUSCANY-708
Project: Tuscany
Issue Type: Bug
Components: Java SDO Implementation
Affects Versions: Java-M2
Environment: All
Reporter: Robbie Minshall
Priority: Minor
TypeHelper.define returns List of Types that includes the DocumentRoot Type
Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-708) Should TypeHelper.define return
List of Types that includes DocumentRootType
Posted by "Fuhwei Lwo (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472843 ]
Fuhwei Lwo commented on TUSCANY-708:
------------------------------------
I think DocumentRoot type was exposed by XSDHelper.define() not TypeHelper.define() method.
I am wondering whether this is any complication by simply removing the DocumentRoot type from the return list of XSDHelper.define(). Any idea?
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Commented: (TUSCANY-708) Should TypeHelper.define return
List of Types that includes DocumentRootType
Posted by "Frank Budinsky (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481167 ]
Frank Budinsky commented on TUSCANY-708:
----------------------------------------
See related discussion in TUSCANY-1177.
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
> Attachments: 708.patch
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Resolved: (TUSCANY-708) Should TypeHelper.define return List
of Types that includes DocumentRootType
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelvin Goodson resolved TUSCANY-708.
------------------------------------
Resolution: Fixed
applied Fuhwei's patch which removes the function that hid the DocumentRoot type from the set of types retuned by SDOUtil.getTypes(TypeHelper,String) method
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
> Attachments: 708.patch
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Updated: (TUSCANY-708) Should TypeHelper.define return List
of Types that includes DocumentRootType
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelvin Goodson updated TUSCANY-708:
-----------------------------------
Patch Info: [Patch Available]
setting patch available flag
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
> Attachments: 708.patch
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Updated: (TUSCANY-708) Should TypeHelper.define return List
of Types that includes DocumentRootType
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelvin Goodson updated TUSCANY-708:
-----------------------------------
Fix Version/s: (was: Java-SDO-Mx)
Java-SDO-M3
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-M3
>
> Attachments: 708.patch
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Updated: (TUSCANY-708) Should TypeHelper.define return List
of Types that includes DocumentRootType
Posted by "ant elder (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-708?page=all ]
ant elder updated TUSCANY-708:
------------------------------
Fix Version/s: Java-M2
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: http://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-M2
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Updated: (TUSCANY-708) Should TypeHelper.define return List
of Types that includes DocumentRootType
Posted by "Fuhwei Lwo (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fuhwei Lwo updated TUSCANY-708:
-------------------------------
Attachment: 708.patch
Since SDOUtil.getTypes() is the only one not exposing DocumentRoot type, I am providing a patch to expose the type to be consistent with others.
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
> Attachments: 708.patch
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Updated: (TUSCANY-708) Should TypeHelper.define return List
of Types that includes DocumentRootType
Posted by "Frank Budinsky (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-708?page=all ]
Frank Budinsky updated TUSCANY-708:
-----------------------------------
Fix Version/s: Java-Mx
(was: Java-M2)
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: http://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-Mx
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
[jira] Commented: (TUSCANY-708) Should TypeHelper.define return
List of Types that includes DocumentRootType
Posted by "Andy Grove (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481053 ]
Andy Grove commented on TUSCANY-708:
------------------------------------
DocumentRoot was mentioned in SDO 2.0.1 and was only relevant to XML documents *without* an XSD. All mentioned of DocumentRoot were removed from SDO 2.1 and XSDHelper.define() should not be returning DocumentRoot.
I have filed a similar bug against the CTS as the current tests expect DocumentRoot to be created when parsing XSD.
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
> Attachments: 708.patch
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Commented: (TUSCANY-708) Should TypeHelper.define return
List of Types that includes DocumentRootType
Posted by "Fuhwei Lwo (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12478762 ]
Fuhwei Lwo commented on TUSCANY-708:
------------------------------------
That's a good point. I think the problem we have now is the inconsistency of handling DocumentRoot type - TypeHelper.define() keeps it but SDOUtil.getTypes() removes it. We need a decision here.
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Commented: (TUSCANY-708) Should TypeHelper.define return
List of Types that includes DocumentRootType
Posted by "Fuhwei Lwo (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481120 ]
Fuhwei Lwo commented on TUSCANY-708:
------------------------------------
I think DocumentRoot type is implementation dependent. CTS should not validate it at all.
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
> Attachments: 708.patch
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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
[jira] Commented: (TUSCANY-708) Should TypeHelper.define return
List of Types that includes DocumentRootType
Posted by "Yang ZHONG (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12472865 ]
Yang ZHONG commented on TUSCANY-708:
------------------------------------
DocumentRoot is like an anonymous type, containing (global) elements, (global) attributes (and build-in Properties such as NameSpace bindings and schemaLocations).
We're including other anonymous types (ones defined inside elements), why not DocumentRoot?
> Should TypeHelper.define return List of Types that includes DocumentRootType
> ----------------------------------------------------------------------------
>
> Key: TUSCANY-708
> URL: https://issues.apache.org/jira/browse/TUSCANY-708
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-M2
> Environment: All
> Reporter: Robbie Minshall
> Priority: Minor
> Fix For: Java-SDO-Mx
>
>
> TypeHelper.define returns List of Types that includes the DocumentRoot Type
> Perhaps is shoudl only include Types that are deifned within the XSD ( i.e CompanyType, DeptartmentType etc )
> SDOUtil.getTypes( scope, uri ) explicidly removes the DocumentRoot Type
> result.remove(((TypeHelperImpl) scope).getExtendedMetaData().getDocumentRoot(ePackage));
> Should the Types returned by TypeHelper.define(...) and SDOUtil(scope, uri ) be consistent ? They probably should at least treat DocumentRoot Type consistently.
> FrankB says: Currently the DocumentRoot contains the global properties but he current SDO spec does not say how they are handled.
--
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