You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Chris Hyzer (JIRA)" <ji...@apache.org> on 2008/12/18 05:14:44 UTC

[jira] Commented: (AXIS2-3364) RESTFul serivce problem when parameters are short

    [ https://issues.apache.org/jira/browse/AXIS2-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12657666#action_12657666 ] 

Chris Hyzer commented on AXIS2-3364:
------------------------------------

Sorry, I dont understand, are you saying that this will not be fixed for minOccurs=0?  And the workaround is to set minOccurs=1?  Thanks, Chris

> RESTFul serivce problem when parameters are short
> -------------------------------------------------
>
>                 Key: AXIS2-3364
>                 URL: https://issues.apache.org/jira/browse/AXIS2-3364
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: adb
>    Affects Versions: 1.3
>            Reporter: takanori
>             Fix For: 1.5
>
>         Attachments: axis2_3364.patch
>
>
> If I develop a RESTFul web service, there is a case that service paramters are not correctly set.
> The service class is :
> ------------------------------------------------------------
> public class RESTfulEcho {
>    public EchoDto echo(Integer id, String message) {
>        EchoDto dto = new EchoDto();
>        dto.setId(id);
>        dto.setMessage(message);
>        return dto;
>    }
> }
> I've tried to call the service like this :
> ------------------------------------------------------------
> http://localhost:8080/axis2/services/RESTfulEcho/echo?message=123
> The parameter "id" is not explicitly set.
> Then the service parameters are :
>  id      ---> 123
>  message ---> null
> When the parameters are explicitly set,
> the service works correctly.
> ------------------------------------------------------------
> http://localhost:8080/axis2/services/RESTfulEcho/echo?id=&message=123
> But, I hope that when the parameters is not explicitly set,
> the parameter is set null or throw a exception.

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