You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Sal Campana (JIRA)" <xm...@xml.apache.org> on 2005/04/07 20:55:28 UTC
[jira] Created: (XMLBEANS-144) XmlObject.set(..) does not behave as expected.
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 2, Version 1.0.4
Environment: Windows
Reporter: Sal Campana
Attachments: test.zip
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Commented: (XMLBEANS-144) XmlObject.set(..) does not behave as expected.
Posted by "Ian Springer (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-144?page=comments#action_66211 ]
Ian Springer commented on XMLBEANS-144:
---------------------------------------
Is there any update on this issue? It's a pretty serious problem for us, since we work with a lot of Web service spec schemas that use a lot of xs:anys, and we are unable to build up the corresponding xbeans using the cursor API without the serialized XML being messed up. For example, if I add a child element <foo:MyAnyElement>...</foo:MyAnyElement> to an existing typed XMLBean <my:TypedElement> that allows xs:any children, then calling toString() afterwards on the typed XMLBean produces:
<my:TypedElement>
<foo:MyAnyElement>
<foo:MyAnyElement>...</foo:MyAnyElement>
</foo:MyAnyElement>
</my:TypeElement>
There is a redundant <foo:MyAnyElement> wrapping the <foo:MyAnyElement> that I added.
Thanks!
Ian
> 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 2, Version 1.0.4
> Environment: Windows
> Reporter: Sal Campana
> Assignee: Jacob Danner
> 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Assigned: (XMLBEANS-144) XmlObject.set(..) does not behave as expected.
Posted by "Lawrence Jones (JIRA)" <xm...@xml.apache.org>.
[ 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: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-144) XmlObject.set(..) does not behave as expected.
Posted by "Sal Campana (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-144?page=history ]
Sal Campana updated XMLBEANS-144:
---------------------------------
Attachment: version-1 output.jpg
This is the output from XmlBeans version 1.0.4
> 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 2, Version 1.0.4
> Environment: Windows
> Reporter: Sal Campana
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Assigned: (XMLBEANS-144) XmlObject.set(..) does not behave as expected.
Posted by "Jacob Danner (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-144?page=history ]
Jacob Danner reassigned XMLBEANS-144:
-------------------------------------
Assign To: 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 2, Version 1.0.4
> Environment: Windows
> Reporter: Sal Campana
> Assignee: Jacob Danner
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-144) XmlObject.set(..) does not behave as expected.
Posted by "Sal Campana (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-144?page=history ]
Sal Campana updated XMLBEANS-144:
---------------------------------
Attachment: test.zip
the test app
> 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 2, Version 1.0.4
> Environment: Windows
> Reporter: Sal Campana
> Attachments: test.zip
>
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
[jira] Updated: (XMLBEANS-144) XmlObject.set(..) does not behave as expected.
Posted by "Sal Campana (JIRA)" <xm...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XMLBEANS-144?page=history ]
Sal Campana updated XMLBEANS-144:
---------------------------------
Attachment: version-2 output.jpg
This is the output from XmlBeans version 2...
> 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 2, Version 1.0.4
> Environment: Windows
> Reporter: Sal Campana
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org