It is typically when new sub-applications come online or the schema gets
modified.
Although you do not want to display this information to the end user, the
person debugging a production system when errors are reported would benefit
from this information if it was available in the logs. Also if it starts to
become a pattern it becomes easier to classify errors. The support person
can say, this is another occurrance of the "expected cityName found
SuiteNumber" problem for example.
It helps smooth out the adoption curve of each release (not to mention the
first release when you start using JAXB).
Kohsuke Kawaguchi
<Kohsuke.Kawaguch To: JAXB-INTEREST_at_JAVA.SUN.COM
i_at_Sun.COM> cc:
Sent by: Subject: Re: Find out what object is missing
Discussion list
for the Java
Architecture for
XML Binding
<JAXB-INTEREST_at_JA
VA.SUN.COM>
05/20/2003 11:32
AM
Please respond to
JAXB-INTEREST
Shashi Garje <SGarje_at_cccis.com> wrote:
> The name of the field that it was expecting and the name of the field
that
> it actually found would be useful.
Would you elaborate on how do you use it? Is it just for your debugging
aid? It seems to me that names of fields are not something you'd want to
present to users.
I agree that it's better than nothing, but it's probably a lot of effort
to do this, and we don't want to find out that it's not that much useful
after we spend a lot of time in it.
regards,
--
Kohsuke KAWAGUCHI 408-276-7063 (x17063)
Sun Microsystems kohsuke.kawaguchi_at_sun.com