You are viewing a plain text version of this content. The canonical link for it is here.
Posted to woden-dev@ws.apache.org by "John Kaputin (JIRA)" <ji...@apache.org> on 2007/01/23 02:43:49 UTC

[jira] Resolved: (WODEN-127) Testcase HTTPBinding-2G fails

     [ https://issues.apache.org/jira/browse/WODEN-127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Kaputin resolved WODEN-127.
--------------------------------

    Resolution: Fixed

Now showing 'green' on the Interop Dashboard.

> Testcase HTTPBinding-2G fails
> -----------------------------
>
>                 Key: WODEN-127
>                 URL: https://issues.apache.org/jira/browse/WODEN-127
>             Project: Woden
>          Issue Type: Bug
>            Reporter: John Kaputin
>         Assigned To: Arthur Ryman
>             Fix For: M7
>
>
> This testcase is fails on the WSDL 2.0 interop Dashboard:
> http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/results/Woden/HTTPBinding-2G/Echo.results.xml?content-type=application/xml
> There seems to be a problem canonicalizing the Woden interchange results (the non-canonical wsdlcm file looks OK).
> The canonical results suggest that Woden has it's Service and Endpoint elements mixed up. Should be 2 services with 1 endpoint in each service, but the Woden canonical results show 1 service with 2 endpoints. 
> When I test this with my own test client it's fine. Here's some output:
> Client: About to read wsdl at location: http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/test-suite/documents/good/HTTPBinding-2G/Echo.wsdl
> Service components:
> EchoService
>     PostEchoHTTPEndpoint
> SafeEchoService
>     EchoHTTPEndpoint

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: woden-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: woden-dev-help@ws.apache.org