You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org> on 2006/10/30 12:28:53 UTC
[jira] Created: (TUSCANY-887) TypeHelper.define() should create an
accompanying global property per type
TypeHelper.define() should create an accompanying global property per type
--------------------------------------------------------------------------
Key: TUSCANY-887
URL: http://issues.apache.org/jira/browse/TUSCANY-887
Project: Tuscany
Issue Type: Bug
Components: Java SDO Implementation
Affects Versions: Java-Mx
Reporter: Kelvin Goodson
Whilst the spec isn't explicit about the behaviour of TypeHelper.define() in this respect, it can be inferred from the specified behaviour of SDO to XSD generation ...
The global element for the type:
• lowercase(TYPE.NAME) is the type name with the first letter converted to lower case
... that the definition of a type using TypeHelper.define(), should also implicitly define a global element to be available using the same naming rules
--
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] Resolved: (TUSCANY-887) TypeHelper.define() should create an
accompanying global property per type
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-887?page=all ]
Kelvin Goodson resolved TUSCANY-887.
------------------------------------
Fix Version/s: Java-Mx
Resolution: Fixed
TypeHelper.define() now defines an accompanying global property per type definition
> TypeHelper.define() should create an accompanying global property per type
> --------------------------------------------------------------------------
>
> Key: TUSCANY-887
> URL: http://issues.apache.org/jira/browse/TUSCANY-887
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-Mx
> Reporter: Kelvin Goodson
> Fix For: Java-Mx
>
>
> Whilst the spec isn't explicit about the behaviour of TypeHelper.define() in this respect, it can be inferred from the specified behaviour of SDO to XSD generation ...
> The global element for the type:
> ? lowercase(TYPE.NAME) is the type name with the first letter converted to lower case
> ... that the definition of a type using TypeHelper.define(), should also implicitly define a global element to be available using the same naming rules
--
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-887) TypeHelper.define() should create an
accompanying global property per type
Posted by "Kelvin Goodson (JIRA)" <tu...@ws.apache.org>.
[ https://issues.apache.org/jira/browse/TUSCANY-887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kelvin Goodson updated TUSCANY-887:
-----------------------------------
Fix Version/s: (was: Java-SCA-Mx)
Java-SDO-M3
> TypeHelper.define() should create an accompanying global property per type
> --------------------------------------------------------------------------
>
> Key: TUSCANY-887
> URL: https://issues.apache.org/jira/browse/TUSCANY-887
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Affects Versions: Java-SCA-Mx
> Reporter: Kelvin Goodson
> Fix For: Java-SDO-M3
>
>
> Whilst the spec isn't explicit about the behaviour of TypeHelper.define() in this respect, it can be inferred from the specified behaviour of SDO to XSD generation ...
> The global element for the type:
> ? lowercase(TYPE.NAME) is the type name with the first letter converted to lower case
> ... that the definition of a type using TypeHelper.define(), should also implicitly define a global element to be available using the same naming rules
--
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