Hmm. Personally, I think that using default values and referential integrity
constraints are a *good* thing, although I think that it's unfortunate that
more tools don't support them. I wouldn't refuse to use them just because
Axis2 ignores them, though. They are still useful as documentation, and if
you have an XML validator, the referential integrity checking can be
invaluable as to figuring out how an incoming message is broken. You can
always supply the default values yourself if you know that your tool (Axis)
doesn't implement them. (Personally, I think that it should support them,
although I also think that there are much higher priority problems to fix at
the moment.)
Derek
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 15, 2006 6:06 PM
> To: axis-user@ws.apache.org
> Subject: Re: Element Default values
>
>
> It's always a bad idea to assume that a processing engine
> will in fact honor default values. As a general rule, avoid
> using default values and referential integrity constraints in
> a schema.
>
> Anne
>
> On 8/15/06, Vinh Tran <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > Are default values supported in Axis2. I have client stubs created
> > from wsdl2java but it doesn't appear to honor the default values on
> > XSD elements.
> >
> >
> >
> > Thanks
>
> -
> 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]
