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

Deepal Jayasinghe updated AXIS2-1424:
-------------------------------------

    Priority: Critical  (was: Major)

Sanka , please have a look at this and if posible try to fix this for 1.3

> Method signatures are incorrect in the sample code given in the "Exception 
> Handling using WSDL Faults" document
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1424
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1424
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: samples, build,site
>    Affects Versions: 1.1
>         Environment: Windows XP, jdk1.5.0_08, Maven 1.0.2, Mozilla Firefox 
> 1.5.0.6
>            Reporter: Evanthika Amarasiri
>            Assignee: Sanka Samaranayake
>            Priority: Critical
>
> Was testing the sample "FaultHandling" of the RC1 version found the following 
> defect
> In the "Exception Handling using WSDL Faults" document, a sample code is 
> given asking the user to insert that part of code into the 
> BankServiceSkeleton.java class
> But this code segment is not valid. 
> final AccountNotExistFault fault = new AccountNotExistFault();
> fault.setAccount(account);
> throw new AccountNotExistFaultMessageException("Account does not exist!", 
> fault);
> The method signatures given in the document are wrong to what is actually 
> given in the actual java classes of the given sample. Therefore, the document 
> has to be updated with the correct segment of code
>  
> The user cannot proceed with the sample until the correct sample code is given

-- 
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to