com.bea.xml.XmlException

Unable to find attachment part for href = id0

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 web117

  • via Oracle Community by 666705, 11 months ago
    Unable to find attachment part for href = id0
  • via Oracle Community by ARPL, 1 year ago
    unable to find binding type for t=list@http://www.oracle.com/webservices/internal/literal : java.util.List
  • via Oracle Community by ARPL, 1 year ago
    unable to find binding type for t=list@http://www.oracle.com/webservices/internal/literal : java.util.List
  • Stack trace

    • com.bea.xml.XmlException: Unable to find attachment part for href = id0 at weblogic.wsee.bind.types.AttachmentBase.deserializeType(AttachmentBase.java:108) at weblogic.wsee.bind.types.TypeRegistry.deserializeType(TypeRegistry.java:103) at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeType(BaseDeserializerContext.java:85) at weblogic.wsee.bind.runtime.internal.BaseDeserializerContext.deserializeWrappedElement(BaseDeserializerContext.java:133) at weblogic.wsee.codec.soap11.SoapDecoder.decodePart(SoapDecoder.java:398) at weblogic.wsee.codec.soap11.SoapDecoder.decodeParams(SoapDecoder.java:236) at weblogic.wsee.codec.soap11.SoapDecoder.decodeParts(SoapDecoder.java:163) at weblogic.wsee.codec.soap11.SoapDecoder.decode(SoapDecoder.java:116) at weblogic.wsee.codec.soap11.SoapCodec.decode(SoapCodec.java:138) at weblogic.wsee.ws.dispatch.server.CodecHandler.decode(CodecHandler.java:138) at weblogic.wsee.ws.dispatch.server.CodecHandler.handleRequest(CodecHandler.java:39) at weblogic.wsee.handler.HandlerIterator.handleRequest(HandlerIterator.java:127) at weblogic.wsee.ws.dispatch.server.ServerDispatcher.dispatch(ServerDispatcher.java:85) 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:173) at weblogic.wsee.server.servlet.BaseWSServlet.service(BaseWSServlet.java:92) at javax.servlet.http.HttpServlet.service(HttpServlet.java:856) at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:223) at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125) 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:3245) 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:2003) at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:1909) at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1359) 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.