You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wink.apache.org by "Bryant Luk (JIRA)" <ji...@apache.org> on 2011/04/12 17:21:06 UTC

[jira] [Created] (WINK-344) Capture variables can be different even though the capture regular expression is the same

Capture variables can be different even though the capture regular expression is the same
-----------------------------------------------------------------------------------------

                 Key: WINK-344
                 URL: https://issues.apache.org/jira/browse/WINK-344
             Project: Wink
          Issue Type: Bug
          Components: Server
    Affects Versions: 1.1.2
            Reporter: Bryant Luk
            Assignee: Bryant Luk


Stefan Witte reported an issue on the mailing list where 2 subresource methods have the same capture regular expression but different capture variable names.
{code}
@Path("test")
public class TestResource {
    @Path("{id})
    @GET
    public String get((@PathParam("id} String id) { ... }

    @Path("{id2})
    @DELETE
    public String delete(@PathParam("id2} String id) { ... }
}
{code}

and in the DELETE method, the id2 would be null.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (WINK-344) Capture variables can be different even though the capture regular expression is the same

Posted by "Bryant Luk (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/WINK-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryant Luk resolved WINK-344.
-----------------------------

    Resolution: Fixed

> Capture variables can be different even though the capture regular expression is the same
> -----------------------------------------------------------------------------------------
>
>                 Key: WINK-344
>                 URL: https://issues.apache.org/jira/browse/WINK-344
>             Project: Wink
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.1.2
>            Reporter: Bryant Luk
>            Assignee: Bryant Luk
>
> Stefan Witte reported an issue on the mailing list where 2 subresource methods have the same capture regular expression but different capture variable names.
> {code}
> @Path("test")
> public class TestResource {
>     @Path("{id})
>     @GET
>     public String get((@PathParam("id} String id) { ... }
>     @Path("{id2})
>     @DELETE
>     public String delete(@PathParam("id2} String id) { ... }
> }
> {code}
> and in the DELETE method, the id2 would be null.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (WINK-344) Capture variables can be different even though the capture regular expression is the same

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WINK-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018892#comment-13018892 ] 

Hudson commented on WINK-344:
-----------------------------

Integrated in Wink-Trunk-JDK1.5 #455 (See [https://hudson.apache.org/hudson/job/Wink-Trunk-JDK1.5/455/])
    Capture variables could be different in subresource methods

Fixes [WINK-344].

Thanks to Stefan Witte for reporting the issue.


> Capture variables can be different even though the capture regular expression is the same
> -----------------------------------------------------------------------------------------
>
>                 Key: WINK-344
>                 URL: https://issues.apache.org/jira/browse/WINK-344
>             Project: Wink
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 1.1.2
>            Reporter: Bryant Luk
>            Assignee: Bryant Luk
>
> Stefan Witte reported an issue on the mailing list where 2 subresource methods have the same capture regular expression but different capture variable names.
> {code}
> @Path("test")
> public class TestResource {
>     @Path("{id})
>     @GET
>     public String get((@PathParam("id} String id) { ... }
>     @Path("{id2})
>     @DELETE
>     public String delete(@PathParam("id2} String id) { ... }
> }
> {code}
> and in the DELETE method, the id2 would be null.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira