Is it possible to have strongly typed HTTP request handlers in Restlet?

You should remove the parameter from the signature Get public User getUser() { String id = getQuery(). GetFirstValue("id"); return new User(id, "Mark", "Kharitonov"); } No need to override the get() methods in this case as the @Get annotation will be automatically detected.

You should remove the parameter from the signature @Get public User getUser() { String id = getQuery(). GetFirstValue("id"); return new User(id, "Mark", "Kharitonov"); } No need to override the get() methods in this case as the @Get annotation will be automatically detected.

OK, so GET bla-bla-bla/user/2 is routed to getUser and if we assume that POST bla-bla-bla/user gets routed to newUser, then getUser and newUser must not be in the same ServerResource, otherwise GET bla-bla-bla/user will be routed to getUser too! Looks like, despite GET and POST speak of the same resource (User) they must be handled by different ServerResource instances. This is kinda disappointing... – mark 2 hours ago.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.