Stuart and Werner- My experience is Castor ignores the map-to element if the class in question is a field in a "higher" (in the XML sense) class. Depending on your mapping, it may be that the <bind-xml> element is overriding the <map-to> element.
Just something to think about. Stephen On 10/26/06, Werner Guttmann <[EMAIL PROTECTED]> wrote:
Stuart, can you please create a new issue at http://jira.codehaus.org/browse/CASTOR, and attach all relevant files so that we can replay (and possibly maybe fix) your problem. Thanks in advance Werner Stuart, Jay Cameron wrote: > Unless I am missing something it appears as though there might be a > problem with the <map-to xml="xxxx"> directive. It appears to work fine > if the element is one or 2 levels deep. However it doesnt work if your > mapping to an element 4 levels deep (not sure about 3) At least this > has been my experience. > > I had a document which looks like > > <envelope> > <header/> > <body> > <find> > <data> > <subdata> > </data> > <data> > <subdata> > </data> > <data> > <subdata> > </data> > </find> > </body> > </envelop> > > when i issue a map-to data, castor will not unmarshall my data > properely, however if i extraxt the xml from the "find" node, > unmarshalling occurs as expected. I am pulling the "data" nodes into an > array list but i dont think that has anything to do with it. > > -- Jay Stuart --------------------------------------------------------------------- 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
