[ http://issues.apache.org/jira/browse/XMLBEANS-144?page=all ]
Lawrence Jones reassigned XMLBEANS-144:
---------------------------------------
Assign To: Wing Yew Poon (was: Jacob Danner)
> XmlObject.set(..) does not behave as expected.
> ----------------------------------------------
>
> Key: XMLBEANS-144
> URL: http://issues.apache.org/jira/browse/XMLBEANS-144
> Project: XMLBeans
> Type: Bug
> Components: XmlObject
> Versions: Version 1.0.4, Version 2
> Environment: Windows
> Reporter: Sal Campana
> Assignee: Wing Yew Poon
> Attachments: test.zip, version-1 output.jpg, version-2 output.jpg
>
> We are experiencing unexpected behaviour when calling the XmlObject.set()
> operation in various ways...
> I've attached an example of this behaviour to demonstrate the issues..
> The scenarios are as follows:
> 1. Set and XmlString (a type which has no name element) - VERSION 1.0.4 only,
> fixed in version 2....
> 2. Calling set using a copy of a strongly typed XmlObject - VER 2 and 1 --I
> show the output without doing a copy and with....
> 3. Calling set using an arbitrary "any". - VER 2 and 1
> 2 and 3 produce similar invalid output, but since they are approached
> differently I included both...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
