javax.xml.soap.SOAPException

Found SOAPElement [<de alerInfoSelectionCriteria xsi:type="n5:DealerInfoParams"> <dealerId>AA0BI</dealerId> <financeSourceId>FS001</financeSourceId> <captiveUserId>foo</captiveUserId> </dealerInfoSelectionCriteria>]. But was not able to find a Part that is r egistered with this Message which corresponds to this SOAPElement. The name of t he element should be one of these[dealerInfoParams]

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 web696

  • via Oracle Community by 3004, 1 year ago
    Found SOAPElement [<de alerInfoSelectionCriteria xsi:type="n5:DealerInfoParams"> <dealerId>AA0BI</dealerId> <financeSourceId>FS001</financeSourceId> <captiveUserId>foo</captiveUserId> </dealerInfoSelectionCriteria>]. But was not able to find a Part
  • via Coderanch by Anthony Smith, 7 months ago
    Found SOAPElement [<v1 xsi:type="xsd:string">411161</v1>]. But was not able to find a Part that is registered with this Message which corresponds to this SOAPElement. The name of the element should be one of these[string] (see Fault Detail for stacktrace): <SOAPpy.Types.structType detail
  • via hivmr.com by Unknown author, 1 year ago
    Found SOAPElement [m:payload xmlns:m="http://www.abc.com/gs/solutions/message" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true" /m:payload]. But was not able to find a Part that is registered with this Message which corresponds to this SOAPElement. Th e name of the element should be one of these[__bea_noname_result]
  • Stack trace

    • javax.xml.soap.SOAPException: Found SOAPElement [<de alerInfoSelectionCriteria xsi:type="n5:DealerInfoParams"> <dealerId>AA0BI</dealerId> <financeSourceId>FS001</financeSourceId> <captiveUserId>foo</captiveUserId> </dealerInfoSelectionCriteria>]. But was not able to find a Part that is r egistered with this Message which corresponds to this SOAPElement. The name of t he element should be one of these[dealerInfoParams] at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:445) at weblogic.webservice.core.handler.InvokeHandler.handleRequest(InvokeHandler.java:74) at weblogic.webservice.core.HandlerChainImpl.handleRequest(HandlerChainImpl.java:125) at weblogic.webservice.core.DefaultOperation.process(DefaultOperation.java:513) at weblogic.webservice.server.Dispatcher.process(Dispatcher.java:150) at weblogic.webservice.server.Dispatcher.doDispatch(Dispatcher.java:125) at weblogic.webservice.server.Dispatcher.dispatch(Dispatcher.java:74) at weblogic.webservice.server.WebServiceManager.dispatch(WebServiceManager.java:98) at weblogic.webservice.server.servlet.WebServiceServlet.serverSideInvoke(WebServiceServlet.java:274) at weblogic.webservice.server.servlet.ServletBase.doPost(ServletBase.java:393) at weblogic.webservice.server.servlet.WebServiceServlet.doPost(WebServiceServlet.java:244) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1053) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:387) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305) at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6291) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:97) at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3575) at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2573) at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178) at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)

    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.