Template index matching mode

[jgustie]

We have a lot of template patterns that look like:

router.attach("/foo/", FooIndexServerResource.class);
router.attach("/foo/{id}", FooServerResource.class);

When we enable extension tunneling this results in an unfortunate URL syntax for the index resource: .../foo/.json

Does it make sense to have something like a Template.MODE_INDEX that only matches the trailing slash if tunneling is disabled but matches the trailing slash OR an extension list if extension tunneling is enabled?

[thboileau]

Hi Jeremy,
If I understand the issue, in case tunneling is unabled, "/foo/.json" will match the "/foof/{id}" template.
Am I right?
This won't happen if you use the other syntax based on the query parameter:
"/foo/?media=json"

[thphuoc]

Hello, I attach an url template as following:
router.attach("/profile?sql={sql}")
Then it cannot understand.
So, my question is: I want to get my param value as a string SQL command then how I have to do?

[Tembrel]

Don't use query parameters in your routing. Instead, use the path part of
the URL:

router.attach("/profile", ProfileServerResource.class);

And get the query parameter value in the resource method:

public class ProfileServerResource extends ServerResource {
// ...
@get("?sql") public Representation lookupProfileBySql() {
String sql = getQuery().getFirstValue("sql", "");
if (sql.isEmpty()) {
// No value supplied for sql parameter, client's fault:
throw new ResourceException(Status.CLIENT_ERROR_BAD_REQUEST,
...);
} else {
// ... do something with the sql value ...
}
}
}

--tim

On Fri, Dec 11, 2015 at 10:19 AM, thphuoc notifications@github.com wrote:

Hello, I attach an url template as following:
router.attach("/profile?sql={sql}")
Then it cannot understand.
So, my question is: I want to get my param value as a string SQL command
then how I have to do?

—
Reply to this email directly or view it on GitHub
#999 (comment)
.