[
https://issues.jboss.org/browse/JBIDE-9829?page=com.atlassian.jira.plugin...
]
Xavier Coulon resolved JBIDE-9829.
----------------------------------
Resolution: Done
The resource validation now supports @Path parameters both at the Type and at the method
levels.
Furthermore, the JAX-RS validation is based on the Eclipse WST Validation v2 extension, so
users can configure it and even decide to enable/disable
@PathParam validation broken
----------------------------
Key: JBIDE-9829
URL:
https://issues.jboss.org/browse/JBIDE-9829
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Environment: JBoss JAX-RS Tools 1.2.2.v20110915-1723-H22-M3
Reporter: Jozef Hartinger
Assignee: Xavier Coulon
Fix For: 3.3.0.M5
Having a class:
@Path("/foo/{id}")
public class Foo {
@Path("/bar")
public void bar(@PathParam("id") String id)
{
// noop
}
}
the following error is recognized by JBoss Tools:
"@PathParam annotation value 'id' does not match any parameter of the same
method or type @Path annotation(s)."
Although the "id" parameter matches the id path parameter defined within
class-level @Path annotation.
Besides, to implement this correctly, it is also important to consider that the JAX-RS
resource may actually be a sub-resource. Thus, a path parameter can be defined on the
resource that delegates to Foo and not on Foo itself.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira