Hi Paul,
this could as well be the reason for the problems we are seeing. Huub,
can you please try to your test case against a 1.3.3 snapshot release
(simply the latest from last weekend).
As far as I remember, I did commit a patch for that issue (and I am
suprised to see that the issue has not been updated).
Kind Regards
Werner
On 27.10.2011 14:16, Paul French wrote:
is this a manifestation of the same problem given at...
http://jira.codehaus.org/browse/CASTOR-2902
Paul French
Kirona Solutions Ltd
Tel: 07803 122 058
E-Mail: [email protected]
Web: www.kirona.com <http://www.kirona.com>
This email and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended
recipient, please contact us on 01625 585511, delete the email
(including any attachment) from your computer and destroy any copies.
Any distribution or copying without our prior permission is prohibited.
Internet communications are not always secure and may be subject to
delays, non-delivery and unauthorised alterations. Therefore,
information expressed in this message is not given or endorsed by Kirona
Solutions Limited ("Kirona") unless otherwise notified by our duly
authorised representative independent of this message. No warranty is
given that this email (including any attachment) is virus free. Any
views or opinions presented are solely those of the author and do not
necessarily represent those of Kirona.
Registered addresses: Kirona Solutions Limited, Barrington House, Heyes
Lane, Alderley Edge, Cheshire. SK9 7LA Registered in England and Wales
No: 04678711
On 27/10/2011 13:05, Werner Guttmann wrote:
Hi,
could you please create a new Jira ticket and attach all this
information, incl. the test case.
Kind Regards
Werner Guttmann
On 25.10.2011 23:02, [email protected] wrote:
I have added a test case in the form of an Eclipse project (adjust
classpath settings).
Furthermore I have done some debugging and found the following piece of
code:
XMLClassDescriptorResolverImpl (line 311):
if (possibleMatches.size() == 1) {
// we have exactly one possible match - that's our result
// (if it has the right namespace, it's an exact match, if not its
// the only possible match)
return (XMLClassDescriptor) possibleMatches.get(0);
}
This means that when I send in a 'raw' xml Fragment in an 'any' element
(xsd) Castor will still find a Descriptor with the same name and assume
it should unmarshall to this element. Well actually it does this once, a
second time it will have 2 descriptors with the same name cached and
then it does check for namespace!?
So basically I cannot send in an XML fragment which is meant to be an
AnyNode when Castor has a Descriptor for an element with the same name
(but different namespace).
This presents me with a difficult problem to solve in our production
code.
How can I tell Castor to leave my 'any' element alone?
Greetings,
Huub
---------------------------------------------------------------------
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
