Steven- 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.
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 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... HTH, Stephen On 4/5/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hi, > > I have a castor.properties containing: > > org.exolab.castor.debug=true > > Which results in output like: > > #startElement: mapping > #startElement: include > #endElement: include > #startElement: mapping > #startElement: class > #startElement: map-to > #endElement: map-to > > etc... is there any way to get castor to print out the attribute values in > these tags? Or any other additional information in the output? > > Also, is there any way to disable the castor default mapping behavior? > It looks like a really useful behavior when you need it, but when I was > trying to debug my mappings, I think it really confused things by giving > me false positives. > > Steven J. Owens > [EMAIL PROTECTED] > > > > ------------------------------------------------- > If you wish to unsubscribe from this list, please > send an empty message to the following address: > > [EMAIL PROTECTED] > ------------------------------------------------- > >
