Stephen,
> No, I don't think there is currently a way to get debug information on
> attributes. I think in the UnmarshalHandler debug is either on or
> off, without much fine-grained control. So I'm afraid it's what you
> see is what you get.
Okay. Maybe when I find time to crack open the code I'll look at
that area.
> As far as turning off the default mapping behavior, I'm going to
> assume you're referring to the introspection that Castor does if a
> class doesn't have a mapping specified. If that's the case, you want
> to look into
Right... handy though it is, during development I'd rather see where
I'm making a mistake.
> org.exolab.castor.xml.util.ClassDescriptorResolverImpl.setIntrospection.
> I'm not quite sure the right way to get your hands on the CDRI
> object, but there might be a way in the Unmarshaller or
> UnmarshallHandler class. Or (now thinking about it) I think you can
> instantiate one and give it to the Unmarshaller...
Ah, I see Unmarshaller.setResolver():
http://www.castor.org/api/org/exolab/castor/xml/Unmarshaller.html#setResolver(org.exolab.castor.xml.ClassDescriptorResolver)
Thanks!
Steven J. Owens
[EMAIL PROTECTED]
-------------------------------------------------
If you wish to unsubscribe from this list, please
send an empty message to the following address:
[EMAIL PROTECTED]
-------------------------------------------------
