org.xml.sax.SAXException

Could not find a codec that understood how to decode [weblogicx.xml.stream .StartElementEvent: message ()] [uri->http://www.w3.org/1999/XMLSchema-instance ln->type qn->xsi:type val->bean:LoanApplication] [uri-> ln->bean qn->xmlns:bean val->java:samples.loan] using http://schemas.xmlsoap.org/soap /encoding/: [ CodecFactory: http://xml.apache.org/xml-soap/literalxml=null, http://schemas.xmlsoap.o rg/soap/encoding/=null, =null]

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web5

  • via Unknown by 3004,
  • Stack trace

    • org.xml.sax.SAXException: Could not find a codec that understood how to decode [weblogicx.xml.stream .StartElementEvent: message ()] [uri->http://www.w3.org/1999/XMLSchema-instance ln->type qn->xsi:type val->bean:LoanApplication] [uri-> ln->bean qn->xmlns:bean val->java:samples.loan] using http://schemas.xmlsoap.org/soap /encoding/: [ CodecFactory: http://xml.apache.org/xml-soap/literalxml=null, http://schemas.xmlsoap.o rg/soap/encoding/=null, =null] at weblogic.soap.codec.CodecFactory.decode(CodecFactory.java:49) at weblogic.soap.codec.SoapMessage.readOperation(SoapMessage.java:209) at weblogic.soap.codec.SoapMessage.read(SoapMessage.java:127) at weblogic.soap.server.servlet.DestinationSendAdapter.doPost(DestinationSendAdapter.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:245) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2279) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1923) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.