[jira] Resolved: (TUSCANY-1113) Extensible namespaces and types that change

["Frank Budinsky (JIRA)" <tu...@ws.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-1113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frank Budinsky resolved TUSCANY-1113.
-------------------------------------

    Resolution: Fixed

Fixed in revision 512383.

You can now obtain helpers that support extensible namespaces by calling SDOUtil.createHelperContext(true).


> Extensible namespaces and types that change
> -------------------------------------------
>
>                 Key: TUSCANY-1113
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1113
>             Project: Tuscany
>          Issue Type: Improvement
>          Components: Java SDO Implementation
>         Environment: Eclipse, EMF 2.2.1
>            Reporter: Christian Landbo Frederiksen
>         Attachments: SDOXSDEcoreBuilder.java, SDOXSDEcoreBuilder.java, SDOXSDEcoreBuilder.java, SDOXSDEcoreBuilder.java, TestTypeChangesAndExtensibleNamespaces.java, TestTypeChangesAndExtensibleNamespaces.java, XSDHelperImpl.java
>
>
> Once an xml-schema with a namespace is defined (XSDHelper) you cannot define other schemas with the same namespace.
> I would like namespaces to be extensible.
> Once the types of a schema is defined you cannot change them by defining an altered version of the schema.
> I realize the dangers of modifying already defined types but I believe i ought to be an option.
> Summary from: http://www.mail-archive.com/tuscany-user%40ws.apache.org/msg00624.html
> An xml schema is uploaded and SDO is used to generate a form for
> submitting data as xml-instances of the schema. 
> New schemas in the same namespace may be added often resulting in new
> forms (this is the first issue where I need to extend existing
> namespaces).
> Xml instances may later be edited again.
> This is the most common use case and SDO seems to support this very
> well. 
> BUT xml schemas may be modified, even individual types.
> This of course flagged some warning signs and schema versions were
> considered. 
> But 'use at own risk' was chosen because of its simplicity. To support
> this strategy a status/mode will be introduced so xml-instances cannot
> be edited while schema is in 'administration'-mode. This ought to handle
> the case with instances at schema-modification time.
> With regards to serialized xml instances any data that is rendered
> invalid with type changes will be reset/deleted as of design. 

-- 
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