Hi, Robert,
first of all, please be so kind to subscribe to the mailing list.
Otherwise, you'll have to wait for my manual approval of any mail and
it's quite likely that I miss something due to some twenty or so spam
mails a day.
On 4/17/07, Robert Eric Reeves [EMAIL PROTECTED] wrote:
Sorry, Jochen. I changed my reply to address and that caused me to appear as
unsubscribed. It should be fixed now.
I was looking at the startElement method, and it has a case statement for
each element child and then an if-else for each element in that case
statement. What was the thinking behind
Has anyone else run across this problem when having a large number of
sub-elements in their XSD?
Thanks!
Robert
Robert Eric Reeves wrote:
My XSD has an element with 55 sub-elements. (Not my fault because I'm
modeling another product's configuration file). This is causing the
startElement
My XSD has an element with 55 sub-elements. (Not my fault because I'm
modeling another product's configuration file). This is causing the
startElement method to get a tad large.
Anybody have any solutions for shrinking this down?
Thanks!
Robert
