On Wed June 17 2009 9:11:03 pm rajla wrote:
Sorry Dan, sometimes I am a a really loser.you are 100% right, the
guilty party was old AXIS stuff server side. After that, I pushed the SAAJ
stuff into the stupid endorsed directory (who came up with that brilliant
idea anyway it is like
Since that error message is coming back in the Fault, that is something on the
server side. Thus, we'd need to see the logs for the server side.
I've never seen that error before either. Bizarre.
Dan
On Tue June 16 2009 5:12:17 pm rajla wrote:
Hello, I am getting the exception
Hey Dan, the problem must be something with Spring 3.0+ and CXF
compatibility. That is all I can think of What sort of server logs?
All the server really does is throw the exception I posted below after it
chokes and pukes. Other than that I don't see anything else in stdout.
Thanks
On Wed June 17 2009 3:21:58 pm rajla wrote:
Hey Dan, the problem must be something with Spring 3.0+ and CXF
compatibility.
Interesting. I haven't tried anything with Spring 3.0 yet.
That is all I can think of What sort of server logs?
All the server really does is throw the
Actually, that error message seems to come from an OLD Axis SAAJ
implementation. Definitely check the server side parts for any leftover Axis
SAAJ things and replace them with a modern implementation. (Sun's SAAJ is what
we test with)
Dan
On Wed June 17 2009 3:21:58 pm rajla wrote:
Hey
Sorry Dan, sometimes I am a a really loser.you are 100% right, the guilty
party was old AXIS stuff server side. After that, I pushed the SAAJ stuff
into the stupid endorsed directory (who came up with that brilliant idea
anyway it is like the JBoss windows registry ha ha ha).
Hello, I am getting the exception
javax.xml.ws.soap.SOAPFaultException: No such Localname for SOAP URI when
implementing signature secruity with WS-Security in CXF. What does this
mean? Anyone have any insights on what I can do to resolve this issue?
Honestly, I don't remember this being
