[ http://issues.apache.org/jira/browse/TUSCANY-515?page=all ]
Frank Budinsky resolved TUSCANY-515. ------------------------------------ Resolution: Invalid > Augmenting / Modifying generated Java SDO Types to enable better conversion > to XSDs > ----------------------------------------------------------------------------------- > > Key: TUSCANY-515 > URL: http://issues.apache.org/jira/browse/TUSCANY-515 > Project: Tuscany > Issue Type: Wish > Components: Java SDO Tools > Reporter: Venkatakrishnan > > I am working on enhancing the Java2WSDL to handle SDOs. One of the things > required in this is the mapping of SDO types to XSDs. > I am following the mapping rules specified in the Java SDO Spec. v2.0.1. Pg. > 107 onwards. > To try out, I picked up the sequences.xsd and generted the SDOs for that. > Next I run each SDO type thro' the tool I have implemented to generate the > XSDs. When I compare the resultant XSD with the original they are not > 'equivalent' in some cases (and I do understand that they will not be equal). > > To get over this incompatibility and arrive at a comparable XSD, the > generated SDOs must capture some additional information or maybe we must have > to change in certain parts, the way it is mapped from XSDs in the first > place. This might also mean that we might end up that the specs have to be > changed or enhanced in the first place. > Whatever be the future course I propose to track all issues related to > SDO-XSD mapping under this JIRA. For each point that I observe as an issue I > shall raise sub-tasks here, within. so that I do not scatter the JIRAs > related to this. -- 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]