I'd like to see relevant element declarations such as <logger> and
<console-handler>.
> Another issue I find problamatic is that it is most of the time a hell
> of a job to locate validation problems based on the message in the
> exception, will this be improved in the future, an indication of the
> linenumber would be a big help.
Thanks for the feedback. I'll file a request-for-enhancement for this so
that this issue will be tracked.
Meanwhile, you can set your often ValidationEventHandler and print the
line number and so on. If I recall correctly, the unmarshaller already
report the line number. It's just the default implementation of
ValidationEventHandler that doesn't report those location information.
> Is what I'm experiencing a bug or am I just overlooking something, at
> least xjc doesn't complain and in the early access this worked (other
> things not with types extending abstract types).
Type substitution (the use of xsi:type) is still unsupported in the FCS.
But since your instance doesn't contain it, I'm not sure if this is a
bug of RI or a bug in XMLSpy or what.
regards,
--
Kohsuke KAWAGUCHI 408-276-7063 (x17063)
Sun Microsystems kohsuke.kawaguchi_at_sun.com