Announcement Announcement Module
Collapse
No announcement yet.
M5 ws-handler error Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    I will check on that for Spring-WS, but didn't you originally have this issue before upgrading to 1.5.1.A?

    If not, can you try to use the same Spring-WS version with the M5 example while also keeping the same <ws-handler/> configuration (including the 'message-factory')? In other words - using everything exactly the same between M3 and M5.

    Comment


    • #17
      Actually it seems i had the issue with the old version i.e 1.5.0 too with SI M5.

      Im not sure exactly what is going wrong and where but the main variables is SI M5 .

      Comment


      • #18
        Do you see the soapAction header on the request WS message in tcpmon?

        Comment


        • #19
          Yes , as follows :
          Code:
          POST http://myserver001/SDSServices/WebService/Gfp1.ASMX HTTP/1.1
          Accept-Encoding: gzip
          Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
          SOAPAction: "http://www.domain.sds.gfp1/GetUSBankHolidays"
          Content-Type: text/xml; charset=utf-8

          Comment


          • #20
            Can you try running the WebServiceDemo in the Spring Integration samples using your M5 environment?

            I just did another line-by-line comparison between the M3 ws-target and M5 ws-handler implementations. Indeed, the only variable is the support for setting the messageFactory as a constructor argument. Since you do see the soapAction header, I really don't see any change that could possible produce this.

            Are there are *any* other differences at all? Java version, JARs on the classpath, different VM args, etc?

            If not, can you paste side-by-side tcpmon results from the M3 and M5 request messages?

            Comment


            • #21
              Yes..I tried the webservice sample provided by SI and it works fine with M5 .

              Here are the tcpmon results for :
              M3 :
              Code:
              POST http://mcib1smdt001/SDSServices/WebService/Gfp1.ASMX HTTP/1.1
              Accept-Encoding: gzip
              Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
              SOAPAction: "http://www.wachovia.sds.gfp1/GetUSBankHolidays"
              Content-Type: text/xml; charset=utf-8
              Content-Length: 249
              Cache-Control: no-cache
              Pragma: no-cache
              User-Agent: Java/1.5.0_11
              Host: mcib1smdt001
              Proxy-Connection: keep-alive
              
              <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><GetUSBankHolidays xmlns="http://www.wachovia.sds.gfp1/">
                <iYear>2008</iYear>
              </GetUSBankHolidays></SOAP-ENV:Body></SOAP-ENV:Envelope>
              M5:
              Code:
              POST http://mcib1smdt001/SDSServices/WebService/Gfp1.ASMX HTTP/1.1
              Accept-Encoding: gzip
              Accept: text/xml, text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
              SOAPAction: "http://www.wachovia.sds.gfp1/GetUSBankHolidays"
              Content-Type: text/xml; charset=utf-8
              Content-Length: 249
              Cache-Control: no-cache
              Pragma: no-cache
              User-Agent: Java/1.5.0_11
              Host: mcib1smdt001
              Proxy-Connection: keep-alive
              
              <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header/><SOAP-ENV:Body><GetUSBankHolidays xmlns="http://www.wachovia.sds.gfp1/">
                <iYear>2008</iYear>
              </GetUSBankHolidays></SOAP-ENV:Body></SOAP-ENV:Envelope>
              I dont see any difference in the 2 traces..

              Comment


              • #22
                Strangely this works fine if deployed on Jboss.
                But it fails consistently on standalone tests without the tcpmon in between. Any ideas ?

                Comment


                • #23
                  Can you compare the versions of all related JARs in your classpath across these environments?

                  For example, these are the correct dependencies for M5:
                  com.sun.xml.messaging.saaj-1.3.0.jar
                  javax.xml.soap-1.3.0.jar
                  javax.xml.stream.1.0.1.jar

                  Comment

                  Working...
                  X