Topic
6 replies Latest Post - ‏2013-04-05T09:29:40Z by SystemAdmin
Jhonmail
Jhonmail
8 Posts
ACCEPTED ANSWER

Pinned topic Error WSWS3047E in testing Web Services

‏2013-03-30T14:58:07Z |
Hi all
again problem with testing Web service generated with EGL: when i run "test with web service explorer" i receive :
The content of the body cannot be displayed in the form view. Please switch to the source view to examine the raw content. if i examine the content i see:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  • <soapenv:Body>
  • <soapenv:Fault>
<faultcode>soapenv:Server.generalException</faultcode>
<faultstring>org.xml.sax.SAXException: WSWS3047E: Error: Impossible deseriallize the element Header of the bean ws.com.pbd.data.TstWebs. The secondary element Header doesn't belong to the space of the names. Very probably, a base of services web of bystanders has sent a message non correct SOAP. Message being parsed:</faultstring>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

attached my egl source file

can some one help me to understand
Updated on 2013-04-05T09:29:40Z at 2013-04-05T09:29:40Z by SystemAdmin
  • Jhonmail
    Jhonmail
    8 Posts
    ACCEPTED ANSWER

    Re: Error WSWS3047E in testing Web Services

    ‏2013-03-30T21:47:30Z  in response to Jhonmail
    Hi all ( i forgot product information)

    EGL tooling and version - RBD 8.0.1.2
    Application type - Rich UI

    again problem with testing Web service generated with EGL: when i run "test with web service explorer" i receive :
    The content of the body cannot be displayed in the form view. Please switch to the source view to examine the raw content. if i examine the content i see:

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

    <soapenv:Body>
    <soapenv:Fault>

    <faultcode>soapenv:Server.generalException</faultcode>
    <faultstring>org.xml.sax.SAXException: WSWS3047E: Error: Impossible deseriallize the element Header of the bean ws.com.pbd.data.TstWebs. The secondary element Header doesn't belong to the space of the names. Very probably, a base of services web of bystanders has sent a message non correct SOAP. Message being parsed:</faultstring>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>

    attached my egl source file

    can some one help me to understand (perhaps my RBD version is old ?)
    • SystemAdmin
      SystemAdmin
      6195 Posts
      ACCEPTED ANSWER

      Re: Error WSWS3047E in testing Web Services

      ‏2013-03-31T01:56:53Z  in response to Jhonmail
      Are you using JAXRPC service with simple content record on Tomcat or non-JavaEE platform ?
      • Jhonmail
        Jhonmail
        8 Posts
        ACCEPTED ANSWER

        Re: Error WSWS3047E in testing Web Services

        ‏2013-04-01T07:39:55Z  in response to SystemAdmin
        Hi Pfyu

        thanks for your reply see attached my prederences's img

        Thanks again

        Attachments

        • Jhonmail
          Jhonmail
          8 Posts
          ACCEPTED ANSWER

          Re: Error WSWS3047E in testing Web Services

          ‏2013-04-02T15:56:25Z  in response to Jhonmail
          Hi Pfyu

          in the meantime I have tried to change from JAXRPC to JAXWS but i receive the same error ..

          any idea how to solve this problem (You o other people ??)

          thanks in advance to all
          p.s. i post also mu WSDL file

          Attachments

          • SystemAdmin
            SystemAdmin
            6195 Posts
            ACCEPTED ANSWER

            Re: Error WSWS3047E in testing Web Services

            ‏2013-04-05T09:21:38Z  in response to Jhonmail
            Hi,

            I assume you are using WAS as the target server runtime. I restored the service skeleton with the attached wsdl and deployed the service to WAS70. But it works in my env.

            See attached project and screen shot.