[
https://issues.apache.org/jira/browse/TUSCANY-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473672
]
Geoff Winn commented on TUSCANY-1073:
-------------------------------------
I have reproduced this problem easily enough by loading the XMLSchema.xsd file.
Unfortunately, that leads on to some difficult problems. That schema file
defines many anonymous types, however the addType method in SDO for C++
requires a type name (and always has). Changing this will be quite invasive
since the type name is currently the standard way to identify and access a
type. Therefore, there is no quick way to make it possible to load the
XMLSchema.xsd file. I would like to defer that problem for the time being and
return to the original issue of generating wsdl with embedded schema.
> Not currently possible to generate WSDL - specifically schema - using SDO
> -------------------------------------------------------------------------
>
> Key: TUSCANY-1073
> URL: https://issues.apache.org/jira/browse/TUSCANY-1073
> Project: Tuscany
> Issue Type: Bug
> Components: C++ SDO
> Affects Versions: Cpp-M3
> Reporter: Matthew Peters
> Fix For: Cpp-M3
>
>
> When I tried to use SDO to generate some wsdl containing a <types> element
> with some schema, I found that I could
> not generate the contents of the schema, specifically those things that are
> in the schema namespace. I can't remember
> quite what happened - either the necessary elements were not in the model or
> not written out, but Ed Slattery explained to me
> at the time that anything in the schema namespace is ignored.
> Please could you fix this so that I can generate wsdl with embedded schema? I
> currently have a bodge where I have to
> generate all the schema part of my wsdl by hand - lots of string handling -
> and then stick it into the wsdl at
> the appropriate point and it is all a bit horrid. Fixing this would help a
> lot.
--
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]
