Quick update....

I spent some time looking at whether we could modify the data type on
the fly at the point at where the Tuscany data types are generated.
However it turns out that the WSDL generation needs to be driven from
the wrapper types and these seem to be generated directly of each Java
method rather than based on the pre-parsed input and output type
structures. So we can go in an re-write the type in question but it
has no effect as the generated wrappers will still be referencing the
unaltered Java type.

Next thing I'm going to look at is to see if it's possible to change
the schema later in the process, i.e. after JAXB has generated the
schema. This looks messy though as we store a schema as a schema
collection, as schema and a DOM all at the same time. I'm not sure how
important these different representations are but I expect we have to
merge them all.

Anyone have any better ideas?

Regards

Simon

Reply via email to