What is vanilla 4.2.3 release?
Alessio Soldano wrote: > > Hi, > this most likely because of the same issue addressed here (linking as > afaics you created that thread): > http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250348#4250348 > Your installation of JBossWS-CXF on top of JBoss AS 4.2.3 is somehow > broken. Here below, the JBossWS-Native saaj impl is being used, which is > wrong when using the CXF based stack. > Check you don't have jbossws-native-* libs in your JBoss server, or try > starting from a vanilla 4.2.3 release, installing jbossws-cxf on that > and looking at the libraries you have at the end of the process. > Cheers > Alessio > > xinxinwang wrote: >> My service has a handler that needs to use SOAPMessage. I deployed my >> service >> to JBoss 4.2.3 GA server. I got an exception after sending a request to >> the >> server: >> >> org.jboss.util.NotImplementedException >> at >> org.jboss.ws.core.soap.SOAPPartImpl.appendChild(SOAPPartImpl.java:298 >> ) >> at >> org.apache.cxf.staxutils.W3CDOMStreamWriter.setChild(W3CDOMStreamWrit >> er.java:114) >> at >> org.apache.cxf.staxutils.W3CDOMStreamWriter.newChild(W3CDOMStreamWrit >> er.java:104) >> at >> org.apache.cxf.staxutils.W3CDOMStreamWriter.writeStartElement(W3CDOMS >> treamWriter.java:132) >> at >> org.apache.cxf.staxutils.StaxUtils.writeStartElement(StaxUtils.java:4 >> 47) >> at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:391) >> at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:379) >> at org.apache.cxf.staxutils.StaxUtils.copy(StaxUtils.java:361) >> at >> org.apache.cxf.binding.soap.saaj.SAAJInInterceptor.handleMessage(SAAJ >> InInterceptor.java:108) >> at >> org.apache.cxf.jaxws.handler.soap.SOAPMessageContextImpl.getMessage(S >> OAPMessageContextImpl.java:78) >> at >> org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.getOpQName(S >> OAPHandlerInterceptor.java:294) >> at >> org.apache.cxf.jaxws.handler.AbstractJAXWSHandlerInterceptor.setupBin >> dingOperationInfo(AbstractJAXWSHandlerInterceptor.java:111) >> at >> org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.createProtoc >> olMessageContext(SOAPHandlerInterceptor.java:235) >> at >> org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessag >> eInternal(SOAPHandlerInterceptor.java:144) >> at >> org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessag >> e(SOAPHandlerInterceptor.java:119) >> at >> org.apache.cxf.jaxws.handler.soap.SOAPHandlerInterceptor.handleMessag >> e(SOAPHandlerInterceptor.java:69) >> at >> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseIntercept >> orChain.java:236) >> at >> org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainIniti >> ationObserver.java:89) >> at >> org.apache.cxf.transport.servlet.ServletDestination.invoke(ServletDes >> tination.java:99) >> at >> org.apache.cxf.transport.servlet.ServletController.invokeDestination( >> ServletController.java:368) >> at >> org.apache.cxf.transport.servlet.ServletController.invoke(ServletCont >> roller.java:183) >> at >> org.apache.cxf.transport.servlet.AbstractCXFServlet.invoke(AbstractCX >> FServlet.java:163) >> at >> org.apache.cxf.transport.servlet.AbstractCXFServlet.doPost(AbstractCX >> FServlet.java:141) >> >> Does anybody know a work-around for this problem? I must use JBoss 4.* >> for >> this service. >> >> Thanks, >> >> Xinxin >> > > > -- > Alessio Soldano > Web Service Lead, JBoss > > > -- View this message in context: http://www.nabble.com/CXF-Handler-and-JBoss-4.2.3-tp25017794p25051189.html Sent from the cxf-user mailing list archive at Nabble.com.
