They are the same XML so there shouldn't be a requirement to do that. I doubt there are any XML serializers in any language which have that as an option, since the XML recommendation specifically says they are equivalent.
Bill Lee
Greenhorn
Joined: Feb 02, 2007
Posts: 20
posted
0
I agree that this shouldn't be an issue, but the way data rules on the other side are causing the error.
This is interpreted as 1 transaction even if they are two. APPARENTLY, this is how it should like to reflect as 2 transactions. I agree with you in that it shouldn't make a difference.
We need to change it to:
<Transacation>
</Transaction>
<Transaction>
<element1></element1>
<element2></element2>
<element3></element3>
</Transaction>
Well, after doing a simple test (which you could have done too) groovy does indeed spit out the undesired XML. Obviously, this goes without saying, but you should fix the back-end to support standards rather than hacking standards to support something broken.
Yea, what Paul said. Assuming that isn't possible you're probably going to have to see if there is a way to modify the behavior of the node builder to achieve what you want. I'm sure there is a way and since it is groovy, it probably isn't too difficult. I just don't personally know how.