[ http://issues.apache.org/jira/browse/AXIS2-370?page=all ]

Thilini Gunawardhana updated AXIS2-370:
---------------------------------------

    Attachment: patch1.jar

IMO following issues were found regarding some test cases in whitemase/round2. 
I have attached complete stack traces and request and response SOAP envelopes 
for a single test case where appropriate. 


1)FrtrRound2InteropTest and SSRound2InteropTest fail, since the service tag is 
missing in the endpoint WSDL. Shall we remove these from itest? 

2)Some test cases in GSRound2InteropTest (in whitemesa/round2) fail giving the 
error as Unexpected end of input block in end tag. Those test cases are 
commented in the submitted patch. 

3)It seems like the endpoints used for KSRoun2InteropTest and 
MSRemRound2InteropTest are removed or deprecated. 

4)NusRound2InteropTest fails as the charset encoding in the declaration part 
(UTF-8) in the returned envelope is different from the charset encoding in the 
XML (ISO-8859-1). 

5)In PSRound2InteropTest, the returned envelope does not contain any valid xml 
content.

6)Removed the test case testR2GBEcho2DStringArray from WFRound2InteropTest, 
since the method echo2DStringArray is not exposed as a service in the given 
WSDL.

> Fixing the interop tests in itest
> ---------------------------------
>
>          Key: AXIS2-370
>          URL: http://issues.apache.org/jira/browse/AXIS2-370
>      Project: Apache Axis 2.0 (Axis2)
>         Type: Improvement
>   Components: Integration
>  Environment: WinXP, JDK 1.4
>     Reporter: Thilini Gunawardhana
>     Assignee: Thilini Gunawardhana
>     Priority: Minor
>  Attachments: patch.jar, patch1.jar
>
> Most of the Interop Tests in Integration/itest fail due to various reasons 
> and I've started fixing those.
> These interop tests have used XMLComparatorInterop to compare the returned 
> Soap Envelope with the expected response. Since this class contains errors, 
> we decided not to use it anymore. Instead, the /compare /method in 
> WhiteMesaInterop class was changed and a new method, /compareXML /is added. 
> So, should we remove XMLComparatorInterop, since it is not used anymore?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to