On Thu, Aug 09, 2001 at 08:48:45PM -0400, David Jencks wrote:
> > It will run into problems with complicated data structures because it
> > pretty much just flattens the XML file into a series of setAttribute
> > calls.
>
> I didn't find this problem, I made a pretty complicated data structure
> load. I used [collections of] inner classes, and the appropriate setXXX
> method created an inner class instance and had the reflective parser call
> the setYYY on the inner class. This was for the rule engine adapter I
> worked on, the rules and other config was all in xml.
Cunning. I guess it's not so much a limitation of the technique
but of my use of it. Perhaps I should factor it out of RARMetaData
and make it generally accessible.
> Still I'll have to look at the Castor stuff.
>
>
> Hmmm, just looked at sun - there's something called JAXB that apparently
> compiles an xml schema into a custom parser that does 2 way translation
> between xml and an object tree. Since this is an impending standard it
> will presumably be the way to go.. for castor as well.
I don't really like the idea of having to regenerate classes whenever
the DTD/schema changes, but JAXB does look kind of cool.
Toby.
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
