Thanks for the comment and the review of the sources. Although it’s probably not the right place to discuss them (there’s another blog just for that ;-), I’ll try to answer your questions.

Yes less4j is focused on REST/JSON and just that.

No, I won’t be posting examples soon, at least not until I get less4j out of alpha, which still entails quite some work (hold your breath a few weeks).

Now regarding the range of HTTP responses available to a web controller, I don’t think that a 404 is appropriate: if the request was passed to the controller by its container then it means that the resource exists (the 404 should be returned by the container when a resource described by a URL is not found).

Regards,

I prefer to do my work in Python, but most of my employment has been for Java, so I know what a pain the Java frameworks can be. Seeing people finding lighter-weight ways to use Java is always encouraging.

From what I can tell less4j is currently focused on REST/JSON applications. Will you be posting some examples soon? Based on your assertion that “200 Ok and 302 Redirect. Failure is not an option on this side.” you obviously have some different ideas about web development. I haven’t done much strictly RESTful development, but I would’ve at least expected the option to send a 404 for accesses to non-existant objects, though I may be missing something.

Also, I noticed there’s a mix of spaces and tabs for indents in Controller.java (possibly others).