Alias Name Support in Tuscany SDO

Currently, alias name support is disabled in SDO, intentionally. The SDOHelperImpl.addAliasName(Type,String) and SDOHelperImpl.addAliasName(Property,String) throw an UnsupportedOperationException when called. Does this function still need to be disabled? When I remove these guards, my test

SDO XMLDocument serialization of Schema Location and NoNamespace Schema Location

When I set either a schema location or a nonamespace schema location on an XMLDocument object, then serialize that object, I do not see either location value represented in the serialized document. The 2.1 spec does not explicitly state that this is a supported behavior, but given the nature of

SDO Type Conversion Unit Test

The unit test case org.apache.tuscany.sdo.test.TypeConversionTestCase exercises the get() methods on a DataObject, validating type conversion functions. What is missing from this test, though, is any conversion testing of the set() methods. This test suite uses the set method to seed the

Re: [SDO] Static SDO Generator problem: elements named internal*

Amita, If I understand what you are saying, I believe you have found one additional condition related to this issue that will precipitate the problem in T-1483. Right? If so, could you post a sample schema that would demonstrate the problem? I'll take a look at it. On Dec 10, 2007 8:32 AM,

Addition for sdo java faq?

After responding to Chris' issue in Tuscany-1925, it occurred to me that this will be an ongoing problem for folks trying to use Sun 1.4 JVMs. Looking back over the dev list history, I see a couple of other times where this has been a problem. Perhaps, we might want to add this to the faq, what

Re: [Java SDO] What should we be attacking?

Kelvin, I have some free cycles, so I'd like to help knock some things off this list for you. I've gone ahead and contributed a patch for 1483. I'll address 1545 as well. I believe that 1384 is already done. On Nov 20, 2007 6:36 AM, kelvin goodson [EMAIL PROTECTED] wrote: What should we be

Re: [SDO Java DISCUSS] Contents of the next SDO release

of getting your requirements into the release is to step forward and supply the fixes. -- Kelvin. On 23/05/07, David Adcox [EMAIL PROTECTED] wrote: Kelvin, I would like to see the multiple namepace issue resolved in the XSD2JavaGenerator tool. This issue is covered in JIRA 1223

Re: [SDO Java DISCUSS] Contents of the next SDO release

requirements into the release is to step forward and supply the fixes. -- Kelvin. On 23/05/07, David Adcox [EMAIL PROTECTED] wrote: Kelvin, I would like to see the multiple namepace issue resolved in the XSD2JavaGenerator tool. This issue is covered in JIRA 1223

SDO support of noContainment for dynamic objects

Static SDO objects may be constructed with a 'noContainment' option using the XSD2JavaGenerator. Is there a similar facility for constructing dynamic data objects?

SDO static codegen needs to support multiple namespaces in a single pass

The SDO static codegen tool (XSD2Java) is currently only able to process a single namespace per invocation. This limitation is problematic when the target schema contains multiple namespaces or includes other schemas with namespaces that are different from the target schema. The user of the

Name mangling of SDO codegen products

SDO codegen tool xsd2java seems to be mangling Java reserved words now, by attaching an underscore (_) to the word. So, 'static' is changed to 'static_' or 'abstract' is changed to 'abstract_'. This has produced an unexpected side-effect of changing, in at least one case, an SDO API entry