[jira] Updated: (TUSCANY-709) Loads DataGraph in designated scope(TypeHelper)
[ https://issues.apache.org/jira/browse/TUSCANY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-709: --- Fix Version/s: (was: Java-SDO-Mx) Java-SDO-M3 Loads DataGraph in designated scope(TypeHelper) --- Key: TUSCANY-709 URL: https://issues.apache.org/jira/browse/TUSCANY-709 Project: Tuscany Issue Type: Improvement Components: Java SDO Implementation Affects Versions: Java-M2 Reporter: Yang ZHONG Priority: Minor Fix For: Java-SDO-M3 Attachments: patch.709 SDOUtil.loadDataGraph doesn't support scope, this improvement tries to address that. TypeHelper#define registers Types with the corresponding TypeHelper instance (scope) and XMLHelper#load utilizes the registered Types from the corresponding scope to instantiate DataObject instances. Unfortunately yet, current SDOUtil.loadDataGraph 2-1. can't designate scope to register serialized Types, 2-2. and can't designate scope to utilize already registered Types in order to instantiate user expected DataObject instances. An example of 2-1 is SerializeTypesTestCase had to // The following is a kludge to force deserialization of metadata into a different TypeHelper (scope) // TBD figure out a proper non-EMF way to do this. Map options = new HashMap(); Object differentFromSerializing = ((TypeHelperImpl) deserializingTypeHelper).getExtendedMetaData(); options.put(XMLResource.OPTION_EXTENDED_META_DATA, differentFromSerializing); This proposal tries to adress scope by 2-1. add new SDOUtil.loadDataGraph(InputStream inputStream,Map options,TypeHelper scope)throws IOException 2-2. deprecate old SDOUtil.loadDataGraph(InputStream inputStream,Map options)throws IOException Any comment is welcomed. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-709) Loads DataGraph in designated scope(TypeHelper)
[ https://issues.apache.org/jira/browse/TUSCANY-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kelvin Goodson updated TUSCANY-709: --- Patch Info: [Patch Available] Loads DataGraph in designated scope(TypeHelper) --- Key: TUSCANY-709 URL: https://issues.apache.org/jira/browse/TUSCANY-709 Project: Tuscany Issue Type: Improvement Components: Java SDO Implementation Affects Versions: Java-M2 Reporter: Yang ZHONG Priority: Minor Fix For: Java-SDO-Mx Attachments: patch.709 SDOUtil.loadDataGraph doesn't support scope, this improvement tries to address that. TypeHelper#define registers Types with the corresponding TypeHelper instance (scope) and XMLHelper#load utilizes the registered Types from the corresponding scope to instantiate DataObject instances. Unfortunately yet, current SDOUtil.loadDataGraph 2-1. can't designate scope to register serialized Types, 2-2. and can't designate scope to utilize already registered Types in order to instantiate user expected DataObject instances. An example of 2-1 is SerializeTypesTestCase had to // The following is a kludge to force deserialization of metadata into a different TypeHelper (scope) // TBD figure out a proper non-EMF way to do this. Map options = new HashMap(); Object differentFromSerializing = ((TypeHelperImpl) deserializingTypeHelper).getExtendedMetaData(); options.put(XMLResource.OPTION_EXTENDED_META_DATA, differentFromSerializing); This proposal tries to adress scope by 2-1. add new SDOUtil.loadDataGraph(InputStream inputStream,Map options,TypeHelper scope)throws IOException 2-2. deprecate old SDOUtil.loadDataGraph(InputStream inputStream,Map options)throws IOException Any comment is welcomed. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-709) Loads DataGraph in designated scope(TypeHelper)
[ http://issues.apache.org/jira/browse/TUSCANY-709?page=all ] Frank Budinsky updated TUSCANY-709: --- Fix Version/s: Java-Mx (was: Java-M2) Priority: Minor (was: Major) Loads DataGraph in designated scope(TypeHelper) --- Key: TUSCANY-709 URL: http://issues.apache.org/jira/browse/TUSCANY-709 Project: Tuscany Issue Type: Improvement Components: Java SDO Implementation Affects Versions: Java-M2 Reporter: Yang ZHONG Priority: Minor Fix For: Java-Mx Attachments: patch.709 SDOUtil.loadDataGraph doesn't support scope, this improvement tries to address that. TypeHelper#define registers Types with the corresponding TypeHelper instance (scope) and XMLHelper#load utilizes the registered Types from the corresponding scope to instantiate DataObject instances. Unfortunately yet, current SDOUtil.loadDataGraph 2-1. can't designate scope to register serialized Types, 2-2. and can't designate scope to utilize already registered Types in order to instantiate user expected DataObject instances. An example of 2-1 is SerializeTypesTestCase had to // The following is a kludge to force deserialization of metadata into a different TypeHelper (scope) // TBD figure out a proper non-EMF way to do this. Map options = new HashMap(); Object differentFromSerializing = ((TypeHelperImpl) deserializingTypeHelper).getExtendedMetaData(); options.put(XMLResource.OPTION_EXTENDED_META_DATA, differentFromSerializing); This proposal tries to adress scope by 2-1. add new SDOUtil.loadDataGraph(InputStream inputStream,Map options,TypeHelper scope)throws IOException 2-2. deprecate old SDOUtil.loadDataGraph(InputStream inputStream,Map options)throws IOException Any comment is welcomed. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (TUSCANY-709) Loads DataGraph in designated scope(TypeHelper)
[ http://issues.apache.org/jira/browse/TUSCANY-709?page=all ] Yang ZHONG updated TUSCANY-709: --- Attachment: patch.709 Please review, any comment is welcomed. Loads DataGraph in designated scope(TypeHelper) --- Key: TUSCANY-709 URL: http://issues.apache.org/jira/browse/TUSCANY-709 Project: Tuscany Issue Type: Improvement Components: Java SDO Implementation Affects Versions: Java-M2 Reporter: Yang ZHONG Attachments: patch.709 SDOUtil.loadDataGraph doesn't support scope, this improvement tries to address that. TypeHelper#define registers Types with the corresponding TypeHelper instance (scope) and XMLHelper#load utilizes the registered Types from the corresponding scope to instantiate DataObject instances. Unfortunately yet, current SDOUtil.loadDataGraph 2-1. can't designate scope to register serialized Types, 2-2. and can't designate scope to utilize already registered Types in order to instantiate user expected DataObject instances. An example of 2-1 is SerializeTypesTestCase had to // The following is a kludge to force deserialization of metadata into a different TypeHelper (scope) // TBD figure out a proper non-EMF way to do this. Map options = new HashMap(); Object differentFromSerializing = ((TypeHelperImpl) deserializingTypeHelper).getExtendedMetaData(); options.put(XMLResource.OPTION_EXTENDED_META_DATA, differentFromSerializing); This proposal tries to adress scope by 2-1. add new SDOUtil.loadDataGraph(InputStream inputStream,Map options,TypeHelper scope)throws IOException 2-2. deprecate old SDOUtil.loadDataGraph(InputStream inputStream,Map options)throws IOException Any comment is welcomed. -- 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
