Jörg Schaible commented on Bug XSTR-733

Sorry for the delay, but some real life problems ate my spare time.

After having a closer look again, the root problem in the test is that the definition of the implicit collection for the list is actually a catch-all, because you did not define the type of objects that are collected in the list. The generic type is not available at runtime and the list can take therefore any object. Now, if the ReflectionConverter detect a element that does not match a member, if looks for an implicit collection/array/map that will take the element. However, there is no defined sequence for such implicit definitions and when it asks for an A it gets by change the bList ... because that one takes any Object. You can solve this by using the 3rd parameter and declare that the list will only take elements of type B.

P.S. Does this type of problem (XML serialisation the same even when objects not the same) suggest that, in general, equals methods in test classes should ideally always be coded? Obviously there's effort in coding them though...

It simply meant that the XML representation of an object is not necessarily unique.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Reply via email to