You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Benson Margulies <bi...@gmail.com> on 2008/02/27 21:56:23 UTC
CXF-1448 request for assistance
While I'm happy to try to serve as Aegis level 1 support, WS Security is
really new to me. Can anyone else wade in here (again)?
Re: CXF-1448 request for assistance
Posted by Daniel Kulp <dk...@apache.org>.
Benson,
On Wednesday 27 February 2008, Benson Margulies wrote:
> While I'm happy to try to serve as Aegis level 1 support, WS Security
> is really new to me. Can anyone else wade in here (again)?
From the stack trace, it doesn't look like it's even getting to the
ws-security stuff. It's barfing in the SAAJInInterceptor while trying
to build the SAAJ model that the security stuff would use.
Thus, you probably can just configure in the SAAJInInterceptor. No
security stuff needed.
THAT said, I still expect you to not be able reproduce it... The stack
trace also points out that it's using the bea Stax parser and not
woodstox which is what we pretty much always test with and have worked
around any issues. I'm not exactly sure how buggy that parser is.
That also said, you should get him to configure in the logging
interceptors so you can see the exact soap message being sent. Thus,
you could see if there really is a namespace issue or not.
--
J. Daniel Kulp
Principal Engineer, IONA
dkulp@apache.org
http://www.dankulp.com/blog