I might just be beating around the bush so in that case just ignore the reply.
see this top level function maybe they help in a way:
Decodes an encoded URI into a string. Top Level
Decodes an encoded URI component into a string. Top Level
Encodes a string into a valid URI (Uniform Resource Identifier). Top Level
Encodes a string into a valid URI component. Top Level
Converts the parameter to a string and encodes it in a URL-encoded format,
where most nonalphanumeric characters are replaced with % hexadecimal sequences.
Whenever I worked with webservice I did it with generated wit objects not XML so
not sure those apply. However I had issues with escaping with URL loader and old
cgi scripts so those functions were helpfull.
If they do not apply to your case ignore this as I said,
Unfortunately Claudiu, this doesn't help me My problem is more webservice-related, i really would like to send some xml, and i'm expecting this is possible because let's imagine you want to create a client, you aren't always able to adapt the server to your client. In my case i could be able to do it, but that would be the ugliest solution.
I tested the xmlSpecialCharsFilter thing but could there be some kind of special command to really escape the < and > characters??
I would really appreciate some help on this problem...
Thank you very much.
But i'm not sure to understand why. Finally, this morning i retried the xmlSpecialCharacterFilter thing and it works.
Is there some kind of cache in the AIR runtime that could have been cleared by restarting my computer?
Or just i didn't set the xmlSpecialCharacterFilter function with the right timing. For those who could encountered the problem, i set it on my webservice object right before the loadWSDL command.