On Mon, 2007-12-31 at 20:40 -0500, Mike Lawrence wrote:
I converted an Xfire SOAP Service to a CXF Simple Service.
My legacy XFire client can no longer call the new CXF service, but SOAPUI
works with both the old XFire and the new CXF server implementation.
This might be an issue of the
I think that the problem might be that you don't have
AegisServiceConfiguration turned on in your service.
If there were the case, there would be a namespace mismatch between the
XFire client and the CXF server until you turned it on.
On Sun, 2007-12-30 at 07:25 -0800, qvall wrote:
Thanks for clarification. How can i make cxf use base64 encoding to
confictual strings then? Any method I should particularly read on? Or
maybe
i have to encode it manually?
You have to force the use of a base64 data type. We don't have an
Once upon a time, in a galaxy far away, the W3C defined XML 1.0. If you
read the spec for XML 1.0, you will find, perhaps to your astonishment,
that some Unicode characters were banished, altogether, from XML. Not
relegated to entities, not prohibited in tag names. Forbidden.
Altogether. I am not
Probably, Mostly you need to filter all the illegal chars from your
contents before feed them to the xml parser
You need to filter all of them, not just 0x07
James
Hi,
Is there any way to translate illegal characters that are in the xml
message?
I'm receiving
There is a dataBinding configuration in jaxws.xsd which used to parse
the jaxws:** tag:
https://svn.apache.org/repos/asf/incubator/cxf/trunk/rt/frontend/jaxws/src/main/resources/schemas/jaxws.xsd
But it has not been implemented . I will get it fixed today or tomorrow.
Use jaxws:dataBinding
