Test case: 1: Create a Jersey resource lets call it TheResource, with a @GET method Lets say it just returns the text "foo". 2: Add a sub resource in TheResource that produces a TheResource with some path lets say the path is "somePath". 3: Load the generated application.wadl in a browser.
This SHOULD produce a WADL according to the JAXRS spec.
Todd
PS:
package pkg;
import javax.ws.rs.GET;
import javax.ws.rs.Path;
public class TheResource {
@GET
public String getText() { return "foo"; }
@Path("somePath")
public TheResource getSubResource() {
return new TheResource();
}
}
What would you expect the WADL to look like? Are you expecting to access?
GET /somePath GET /somePath/somePath GET /somePath/somePath/somePath …
If there are infinitely many resources, shouldn’t the WADL be infinite? :-)
Is this a real use case or an academic exercise?
— Santiago …or even better, Todd, provide a reproducible test case and bug fix, as this is what open source is about… ;-) -Markus I am trying to use jersey to develop a wiki, and when I include a recursive sub resource, application.wadl does not generate, I get a stack overflow. Please fix, or recommend an alternative.
jersey-dev mailing list
jersey-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jersey-dev
--
_______________________________________________ jersey-dev mailing list jersey-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jersey-dev
|
