I don't have a standalone test case yet, but they were able to find an important clue. When they stepped into the Castor source, they saw that when it started working on an attribute of type "xs:IDREF", it reported that it was unrecognized. When they changed their schema so the attribute was instead an "xs:string", it didn't fail.
> -----Original Message----- > From: Karr, David > Sent: Friday, March 02, 2007 10:16 AM > To: [email protected] > Subject: [castor-user] Getting "Unable to resolve ID for > instance of class 'java.lang.String' due to the following > error: Unable to resolve ClassDescriptor." > > V0.9.6, JDK 1.4.2. > > A colleague of mine is getting the following error when he > marshals an object to XML: > > Unable to resolve ID for instance of class 'java.lang.String' > due to the following error: Unable to resolve ClassDescriptor. > > He's using a pretty simple binding file to deal with some > types and elements with the same name, so I don't think it's > an issue with the binding file. > > I looked at the definition of the element associated with the > object and followed the trail of definitions. The only thing > that strikes a chord with me is that one of the elements > defines an attribute whose type is a restriction on xs:string > (defines the maxlength and allowable patterns). > Does that point to the problem, or not? > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
