When using a client handler, the ampersand char is not encoded properly: "&" becomes "&" instead of "&".
This was a known behavior more than 1 year ago (
https://jax-rpc.dev.java.net/servlets/ReadMsg?listName=users&msgNo=1604) which should have been fixed, but I still get this error with JWSDP1.5 (wscompile 1.1.2_01, build R40).
Can anyone confirm this? Is this a regression or it has been never fixed in the official release?