I butchered the schema mostly to see how it effected the process. I
used an external jxb binding in my R&D. What I'd like to do now is see
how to take the draft schema and get that to compile. Unfortunately it
had some issues with my client libraries not sending proper DSMLv2.
Quick question: if I have a <sequence> in my schema, but I really don't
care if the children are in sequence, is there a way through a custom
binding to get around this? Or to completely turn off validation?
------------------------------------------------------------------------
--------------------------
Marc Boorshtein
Sr. Software Engineer, Octet String
marc.boorshtein_at_octetstring.com
On Aug 30, 2004, at 9:50 AM, Ryan Shoemaker - JavaSoft East wrote:
> Marc Boorshtein wrote:
>
>> Thanks for the response! I had found the tutorial and adding the
>> "Element" suffix to conflicts worked as described. I need to
>> re-review what I did, as during the process of understanding how
>> jaxb binding works I butchered the schema. There were still a few
>> things I was shady on, but I will need to review my notes. Thanks
>> for the help!
>
> No problem. If you're comfortable with XPath, it might be better for
> you to use an external customization file so you don't risk breaking
> your schema. Take a look at the $JAXB_HOME/samples/external-customize
> sample app.
>
> --Ryan
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
> For additional commands, e-mail: users-help_at_jaxb.dev.java.net
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jaxb.dev.java.net
For additional commands, e-mail: users-help_at_jaxb.dev.java.net