Hi Ned,
>
> - using UNIX style line separation.
> Type not found for element: ResultData
> Type not found for element: ContextData
>
> In the dtd that generated this, it had
> <!ELEMENT ResultData ANY>
> <!ELEMENT ContextData ANY>
It is normal that Castor complains on your schema.
Your schema defines an element <element name="resultData"/>
without defining a type for it, so Castor assumes you have
somewhere a class ResultData...it doesn't reflect at all you DTD.
Which tool are you using to convert your DTD to an XML Schema, given the
Schema it seems not to be a nice tool :+(...it is missing some XML Schema
good practices.
<!ELEMENT ResultData ANY>
corresponds to
<element name="ResultData">
<complexType>
<any .../>
</complexType>
</element>
> Now, failures occur in the compliation from
>
> a) The DTD describes an elemnt 'Exception' This confuses Castor, for
> good reason. Since Java would complain anyways, I've changed it to
> WfException. (So, this isn't a problem with castor, rather with
> the WfMC spec. I mearly want a forum to complain. :-)
No problem, we can handle your complains ;+)
In fact we are working on a Source Generator Binding File that will allow you
to choose the name of the class generated given the XML Schema element name (and
other
features...), it will be ready for the next version of Castor.
> b) It cannot resolve ResultData.class. I'm guessing this is where I
> have to create this? I figure Castor would stub-out an element of
> type <any> for the ResultData. What is the proper why to handle
> this? (Rather than change it to type <text>)
See before
> c) Many warnings that org.xml.sax.DocumentHandler is deprecated. Now,
> the results still work/compile. I guess this isn't a real problem
> currently since it does work. But what I don't understand is that
> Xerces wants to use ContentHandler instead, which is sax2. Are
> they (Xerces) going to stop supporting sax in the future, and only
> support sax2? I understand that Castor want sax instead of sax2
> but what is the future of Sax. (Perhaps there's a better place to
> ask this then here... pointers?) What parsers do people suggest to
> use with Castor? I've always assumed Xerces in the freeworld. Other
> choices that may be better?
Actually if you want precision on Xerces, go to the Xerces mailing-list, for SAX
you can
ask on the XML-DEV mailing list.
Actually a new release of SAX2 is available and contain bug fixes. SAX2 is
really a standard
that won't be abandoned (I guess :+)) by any parser.
But don't worry for the Castor side since we are going to provide our own
event-based
API with all the necessary adapters to different XML APIs.
Hope this helps,
Arnaud
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
