Well, since we use wrapped doc-literal, our services are also able to be invoked REST-style, so I use a JSP page with query strings for quick and easy testing, hence the GET. Sorry about that.
I will look into using a real XML invoking method, perhaps even an actual test client... -Chris W. -----Original Message----- From: Daniel Kulp [mailto:[EMAIL PROTECTED] Sent: Monday, June 09, 2008 2:37 PM To: users@cxf.apache.org Subject: Re: Bug CXF-830 closed, but I still have it. On Jun 9, 2008, at 2:11 PM, Wolf, Chris (IT) wrote: > Ok, I was able to try the 2.1 release, I also commented out the > explicit > > SAAJ interceptor from the config file, as you suggested. I am STILL > getting the NullPointerException. I notice that the WSS4J interceptor > is incorporating the SAAJ interceptor implicitly. > > BTW, why was CXF-830 closed with "Won't Fix"? I seem to be getting > it, even with the latest release. It was marked won't fix because when they updated from 2.0 to the latest 2.0.x (probably 2.0.3 at the time), the problem went away. Thus, it was assumed already fixed. From the stack trace, the XMLStreamReader is null. I have NO idea how that would occur. Actually.... > org > .apache.cxf.transport.servlet.AbstractCXFServlet.doGet(AbstractCXFSer > vlet.java:152) Why is there a "GET" request? SOAP messages should be POST's. The SAAJ stuff (and wss4j stuff), etc... won't work with a GET. Dan > Can you offer any debugging strategies > short of setting up CXF source-level build/debug? > > Thanks, > > -Chris W. > > INFO: Interceptor has thrown exception, unwinding now > java.lang.NullPointerException > at > org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java:662) > at > org > .apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInI > nterceptor.java:110) > at > org > .apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JI > nInterceptor.java:88) > at > org > .apache.cxf.ws.security.wss4j.WSS4JInInterceptor.handleMessage(WSS4JI > nInterceptor.java:60) > at > org > .apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC > hain.java:221) > at > org > .apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiati > onObserver.java:78) > at > org > .apache.cxf.transport.servlet.ServletDestination.invoke(ServletDestin > ation.java:92) > at > org > .apache.cxf.transport.servlet.ServletController.invokeDestination(Ser > vletController.java:214) > at > org > .apache.cxf.transport.servlet.ServletController.invoke(ServletControl > ler.java:113) > at > org > .apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCXFSe > rvlet.java:170) > at > org > .apache.cxf.transport.servlet.AbstractCXFServlet.doGet(AbstractCXFSer > vlet.java:152) > > Again, here is my config: > <jaxws:endpoint > id="secadmin" > implementor="com.ms.ibd.svcscore.secadmin.SecAdminImpl" > wsdlLocation="WEB-INF/wsdl/secadmin.wsdl" > address="/secadmin"> > <jaxws:features> > <bean class="org.apache.cxf.feature.LoggingFeature"/> > </jaxws:features> > <jaxws:inInterceptors> > <bean > class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor"/> > </jaxws:inInterceptors> > </jaxws:endpoint> > > -----Original Message----- > From: Daniel Kulp [mailto:[EMAIL PROTECTED] > Sent: Friday, June 06, 2008 5:13 PM > To: users@cxf.apache.org > Subject: Re: Bug CXF-830 closed, but I still have it. > > > > Not really sure what would cause that. That said, with CXF 2.1, you > don't need to configure in the SAAJInInterceptor. The > WSS4JInInterceptor will automatically do that if needed. I'm not > sure if that would change anything (it shouldn't). > > Dan > > > > > On Jun 6, 2008, at 5:03 PM, Wolf, Chris (IT) wrote: > >> I am trying to configured the out-of-the-box CXF security >> interceptors, but I am getting a NullPointerException: >> >> INFO: Interceptor has thrown exception, unwinding now >> java.lang.NullPointerException >> at >> org.apache.cxf.staxutils.StaxUtils.readDocElements(StaxUtils.java: >> 658) >> at >> org >> .apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInI >> nterceptor.java:110) >> at >> org >> .apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJInI >> nterceptor.java:1) >> at >> org >> .apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorC >> hain.java:220) >> [...] >> >> Here, I have no actions configured, so the processing should just be >> pass-through to validate my setup before trying to actually configure >> security. >> >> <jaxws:endpoint >> id="secadmin" >> implementor="com.ms.ibd.svcscore.secadmin.SecAdminImpl" >> wsdlLocation="WEB-INF/wsdl/secadmin.wsdl" >> address="/secadmin"> >> <jaxws:features> >> <bean class="org.apache.cxf.feature.LoggingFeature"/> >> </jaxws:features> >> <jaxws:inInterceptors> >> <bean >> class="org.apache.cxf.binding.soap.saaj.SAAJInInterceptor"/> >> <ref bean="wss4jInConfiguration"/> >> </jaxws:inInterceptors> >> </jaxws:endpoint> >> <bean id="wss4jInConfiguration" >> class="org.apache.cxf.ws.security.wss4j.WSS4JInInterceptor"> >> <!-- property name="properties"> >> <map> >> <entry key="action" value="Timestamp"></entry> >> </map> >> </property--> >> </bean> >> >> >> I found this problem logged as a bug, but closed with "won't fix". >> https://issues.apache.org/jira/browse/CXF-830 >> >> I looked at: >> http://cwiki.apache.org/CXF20DOC/ws-security.html >> >> and that doesn't offer troubleshooting advice. >> >> I am using a snapshot from April. >> >> >> Regards, >> >> Chris Wolf >> -------------------------------------------------------- >> >> NOTICE: If received in error, please destroy and notify sender. >> Sender does not intend to waive confidentiality or privilege. Use of >> this email is prohibited when received in error. > > --- > Daniel Kulp > [EMAIL PROTECTED] > http://www.dankulp.com/blog > -------------------------------------------------------- > > NOTICE: If received in error, please destroy and notify sender. > Sender does not intend to waive confidentiality or privilege. Use of > this email is prohibited when received in error. --- Daniel Kulp [EMAIL PROTECTED] http://www.dankulp.com/blog -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
