OK, just wanted to make sure I hadn't missed a discussion on how to do
this with dynamic SDOs.
You know, one issue I noticed when looking at this with static SDOs is
the way that SDO makes it hard for you
to programmatically go from static SDO to XSD. Looking at the SDO
source I think it was the code in
org.apache.tuscany.sdo.helper.SchemaBuilder.buildSchema() which was responsible:
throw new IllegalArgumentException("Cannot generate
XSD since SDO Type '" +
dataType.getName() + "' was orginally
generated from XSD. Use original XSD");
On Feb 5, 2008 3:55 AM, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
> Scott Kurz wrote:
> > When you wrote:
> >
> > - The generator should use the databinding metadata (including any
> > knowledge of handwritten XSD representing the business data and
> > generation capabilities like the SDO XSDGenerator) to generate proper
> > XSD in the WSDL.
> >
> > How were you thinking a particular XSD would be associated with a
> > generic DataObject on a Java intf? What
> > metadata would we be using as input here?
> >
> [snip]
>
> I was thinking about static SDOs.
>
> Java method updateCustomer(DataObject anObject) would translate to
> WSDL operation updateCustomer [ XSD xsd:any ]
>
> but Java method updateCustomer(Customer customer) would translate to
> WSDL operation updateCustomer [ XSD cust:Customer ]
>
>
> --
> Jean-Sebastien
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
