scalaxb.ParserFailure

Error while parsing <ns2:SearchPartnerResponse xmlns: //| ns2="http://hub.victoria.pt/InsurancePartnerService/"> //| <ReturnInfo> //| <Code>999</Code> //| <Message>Failed to execute phase</Message> //| </ReturnInfo> //| </ns2:SearchPartnerResponse>: parser error "end of input" while parsin //| g /{http://hub.victoria.pt/InsurancePartnerService/}SearchPartnerResponse/Re //| turnInfo //| ^

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 web14

  • via Google Groups by João Ferreira, 6 months ago
    Error while parsing <ns2:SearchPartnerResponse xmlns: //| ns2="http://hub.victoria.pt/InsurancePartnerService/"> //| <ReturnInfo> //| <Code>999</Code> //| <Message>Failed to execute phase</Message
  • via Google Groups by Viktor Hedefalk, 6 months ago
    Error while parsing <operation name="getValidCodes" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://service.linkon.se/gtssales/v1_14" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl
  • Error while parsing <operation name="getValidCodes" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://service.linkon.se/gtssales/v1_14" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns="http://schemas.xmlsoap.org/wsdl
  • Stack trace

    • scalaxb.ParserFailure: Error while parsing <ns2:SearchPartnerResponse xmlns: //| ns2="http://hub.victoria.pt/InsurancePartnerService/"> //| <ReturnInfo> //| <Code>999</Code> //| <Message>Failed to execute phase</Message> //| </ReturnInfo> //| <
    • s2:SearchPartnerResponse>: parser error "end of input" while parsin //| g /{http://hub.victoria.pt/InsurancePartnerService/}SearchPartnerResponse/Re //| turnInfo //| ^ at scalaxb.package$.fromXML(scalaxb.scala:15) at repl$$anonfun$main$1.apply$mcV$sp(repl.scala:23)

    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.