Yep, precisely what I needed, thanks!
So, here we have the culprits.
Exhibit A:
<Description>Multiplier applied to demand & summation values</Description>
Exhibit B:
<Description>Divsior applied to demand & summation values</Description>
This to me looks actually like a Eagle200 bug, in that it posts invalid XML. The ‘&’ characters need to be escaped as
&
otherwise any XML parser (including XStream that the binding uses) will probably croak. You may wanna open a bug report with the Rainforest Eagle folks to ask them to properly format their XML replies. You can use the XML in your post, the XML standard [ Extensible Markup Language (XML) 1.0 (Fifth Edition) ] and this thread as reference.
If you give me a few minutes, I’ll see what I can do as a temporary work around, and I’ll post back here if I figure something. However, this should be fixed in the Eagle device.
Cheers,
-Th