1 Reply Latest reply on Nov 21, 2006 2:40 PM by Daniel Brum

    BindException

    Bob Smith Newbie

      I have copied the loanbroker example and made changes. I am getting the following error when performing the equivalent action of submitting the loan from the web page. I know this isn't really an ESB issue, but can anyone tell me why I may get the error below. I don't want to include all my environment/configuration details in this post as, to be honest, I'm not sure what would be relevant. I'm completely new to Web Services.

      javax.xml.rpc.JAXRPCException: org.jboss.ws.binding.BindingException: javax.xml.bind.JAXBException: Failed to parse source: Requested element {http://localhost/pdtest}xname is not allowed in this position in the sequence. The next element should be {http://localhost/pdtest}address
      


      The incoming SOAP message looks fine to me:
      2006-11-17 10:31:44,390 DEBUG [org.jboss.ws.server.ServiceEndpoint] Incomming SOAPMessage
      <soapenv:Envelope xmlns:soapenv='http://schemas.xmlsoap.org/soap/envelope/' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
       <soapenv:Header/>
       <soapenv:Body>
       <PlaceOrder xmlns='http://localhost/pdtest'>
       <WebOrder_1 xmlns=''>
       <ns1:xname xmlns:ns1='http://localhost/pdtest'>Bob Smith</ns1:xname>
       <ns2:address xmlns:ns2='http://localhost/pdtest'>1 West Street, London</ns2:address>
       <ns3:email xmlns:ns3='http://localhost/pdtest'>bob.smith@place.com</ns3:email>
       <ns4:product xmlns:ns4='http://localhost/pdtest'>333</ns4:product>
       <ns5:quantity xmlns:ns5='http://localhost/pdtest'>1</ns5:quantity>
       </WebOrder_1>
       </PlaceOrder>
       </soapenv:Body>
      </soapenv:Envelope>
      


      Thanks,
      Bob

        • 1. Re: BindException
          Daniel Brum Novice

          Hi Bob, sorry for the delay in answering but we are currently all off-site at a JBoss event.

          Can you paste your full stack trace from JBoss? This looks like a JBossWS issue possibly, did you change anything in the pojo web service class and then not regenerate the client side WS classes?