Currently i don't see any way to workaround this right now :/
Triming/no triming string values in soap message is a little tricky.
What data should be trimed and which not ? If someone send SOAP
message which is formated so field can contains "\n value\n"
value, which part should be trimed ? :)
Probably we can introduce some configuration option DONT_TRIM_STRINGS,
so raw string will be returned, but we need to take a look at this
little deeper.
On 3/13/07, Andrzej Doyle <[EMAIL PROTECTED]> wrote:
Hi all,
I've recently run up against the issue described by XFIRE-529 in JIRA
(basically, leading/trailing whitespace is trimmed from strings sent as
parameters/return values). As noted on the bug, my diagnosis of the cause is
the same as Andy's.
Does anyone know of a configuration-level or client code workaround for this
issue? Hacking the code to fix this specific issue is fairly easy, but I'd
really rather not run custom builds if I can avoid it. Additionally, I don't
know enough about the XFire internals to be able to present a true fix for
the issue (the getValue() method that causes the problem is called from 53
places, so it's pretty involved). Has anyone else successfully overcome this
limitation?
Thanks in advance,
Andrzej
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
