java.lang.IllegalStateException

marshallElement not supported for Soap Encoding

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

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

Solutions on the web18878

  • via Oracle Community by 666705, 11 months ago
    marshallElement not supported for Soap Encoding
  • via Stack Overflow by Yossi
    , 1 year ago
    Method 'jsxGet_encoding' was not found for encoding property in com.gargoylesoftware.htmlunit.javascript.host.css.CSSCharsetRule
  • Async not supported for this request
  • Stack trace

    • java.lang.IllegalStateException: marshallElement not supported for Soap Encoding at weblogic.wsee.bind.runtime.internal.EncodedSerializerContext.marshalElement(EncodedSerializerContext.java:67) at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.internalSerializeElement(BaseSerializerContext.java:195) at weblogic.wsee.bind.runtime.internal.BaseSerializerContext.serializeElement(BaseSerializerContext.java:126) at weblogic.wsee.codec.soap11.SoapEncoder.encodePart(SoapEncoder.java:272) at weblogic.wsee.codec.soap11.SoapEncoder.encodeReturn(SoapEncoder.java:188) at weblogic.wsee.codec.soap11.SoapEncoder.encodeParts(SoapEncoder.java:175) at weblogic.wsee.codec.soap11.SoapEncoder.encode(SoapEncoder.java:102) at weblogic.wsee.codec.soap11.SoapCodec.encode(SoapCodec.java:102) at weblogic.wsee.ws.dispatch.server.CodecHandler.encode(CodecHandler.java:103) at weblogic.wsee.ws.dispatch.server.CodecHandler.handleResponse(CodecHandler.java:50) at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:242) at weblogic.wsee.handler.HandlerIterator.handleResponse(HandlerIterator.java:226) at weblogic.wsee.ws.dispatch.server.ServerDispatcher.callHandleResponse(ServerDispatcher.java:142) at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:115) at weblogic.wsee.ws.WsSkel.invoke(WsSkel.java:80) at weblogic.wsee.server.servlet.SoapProcessor.handlePost(SoapProcessor.java:66) at weblogic.wsee.server.servlet.SoapProcessor.process(SoapProcessor.java:44) at weblogic.wsee.server.servlet.BaseWSServlet$AuthorizedInvoke.run(BaseWSServlet.java:165) at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:84) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:225) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:127) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283) at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3214) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:1983) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1890) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1344) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209) at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

    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

    You’re the first here who have seen this exception.