Tried a workaround for this, by removing description, and for some mapping files it worked. Problem that just occurred is that in one of the mapping files one of the classes has "description" field, and Castor 1.3.2 doesn't like that either:
Unable to find FieldDescriptor for 'description' in ClassDescriptor of class. Why doesn't Castor like "description" elements and fields in mapping files? Regards, Stevo. On Thu, Sep 29, 2011 at 5:17 PM, Stevo Slavić <[email protected]> wrote: > Hello Castor users, > > Maintaining a project I updated Castor to 1.3.2, and now Castor > complains on unchanged valid Castor mapping files, reporting for all > description elements (global one under mapping root element, but also > description elements within class elements) following error message: > > Unable to find FieldDescriptor for 'description' in ClassDescriptor of > mapping. > > description element is allowed according to following Castor mapping > xsd: http://www.castor.org/mapping.xsd > > Couldn't find JIRA ticked opened for this. Is anyone experiencing this > unwanted behavior? > > Regards, > Stevo. > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
