[
https://issues.jboss.org/browse/JBIDE-11229?page=com.atlassian.jira.plugi...
]
Xavier Coulon commented on JBIDE-11229:
---------------------------------------
There's an error in the given example, there's no need for brackets in the
@PathParam annotation value.
It should be as below:
{code}
@PUT
@Path("{param2}")
public Response update(@Context HttpServletRequest requestContext, Bar bar,
@PathParam("param2") String param2) throws Exception { ... }
{code}
JAX-RS validation problem marked as Error instead of Warning - Edge
Case
------------------------------------------------------------------------
Key: JBIDE-11229
URL:
https://issues.jboss.org/browse/JBIDE-11229
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.Beta1
Environment: Win7 64bit
Eclipse 3.7.2 64bit
JBoss JAX-RS
Tools 1.2.2.v20120306-1559-H77-Beta1 org.jboss.tools.ws.jaxrs.feature.feature.group JBoss
by Red Hat
JBoss Maven
Integration 1.3.0.v20120307-0425-H80-Beta1 org.jboss.tools.maven.feature.feature.group JBoss
by Red Hat
JBoss Maven JAX-RS
Configurator 1.3.0.v20120307-0425-H80-Beta1 org.jboss.tools.maven.jaxrs.feature.feature.group JBoss
by Red Hat
JBoss WebServices
Tools 1.2.2.v20120306-1559-H77-Beta1 org.jboss.tools.ws.feature.feature.group JBoss by Red
Hat
Reporter: Ron Ratovsky
Assignee: Xavier Coulon
Fix For: 3.3.0.Beta2
Following JBIDE-11070's fix and some extra code in our project, there's an
edge-case that wasn't covered by the previous fix.
Unfortunately, I can't point out to exactly what's causing the issue, but I can
possibly guide to it.
Take the following code sample:
@Path("/foo/{param1}/bar")
public class FooRestService {
@PUT
@Path("{param2}")
public Response update(@Context HttpServletRequest requestContext, Bar bar,
@PathParam("{param2}") String param2) throws Exception { ... }
}
This code will generate the following error:
Description Resource Path Location Type
Invalid @PathParam value: expected '[param1,
param2]' FooRestService.java /path/to/class line XX JAX-RS Problem
I imagine this is due to the following possible reasons:
1. There's a {param} on the class's @Path annotation (first time we have it).
2. There's more than one {param} that's supposed to be included in the method
signature.
3. A combination of the two above reasons.
--
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