I could reproduce this issue with Spark using ad-hoc messages. <message to="recv@host" id="XRk8p-X"> <body><item/><item/></body> </message> works fine while <message to="lg@jivesoftware.com" id="XRk8p-X"> <body><item/><item/></body> </message> will disconnect the sender.
Environment
None
Activity
Show:
MattM
March 19, 2007 at 4:39 AM
It appears we were wrong on this one – the characters are valid XML and we should deal with this case. A patch and test cases have been kindly created by a community member:
I could reproduce this issue with Spark using ad-hoc messages.
<message to="recv@host" id="XRk8p-X">
<body><item/><item/></body>
</message>
works fine while
<message to="lg@jivesoftware.com" id="XRk8p-X">
<body><item/><item/></body>
</message>
will disconnect the sender.