Shantanu Kumar
unread,Sep 21, 2009, 5:07:20 PM9/21/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to bitumenframework, b.g...@gmail.com, b.g...@paisa.com
Hi,
JWebMVC 0.1-alpha2 is uploaded. From the CHANGES.txt file for 0.1-
alpha2 version:
- Routes (PUT & POST only) can be specified with what content-type
payload
(with request) do they consume. PUT and POST restriction is added.
- User-assisted Content Negotiation (conneg) support. You can now
specify
for every route what content-type, charset, encoding or language it
can
produce response in. The route matcher will automatically (based on
acceptable quality rating, as per RFC 2616) choose the appropriate
route.
- Replaced the IAction methods executeError(), postExecuteError() and
postResultError() with a simple error(errorSource) method. This is
to
simplify the concept of action-sequence walking for the user.
- Action sequence walker now calls error-handler when an error occurs
while writing out the response.
###########
Known bugs:
###########
- RFC 2616 (section 14.1) prescribes an explicit quality rating
(example:
"level=1" in "Accept: text/*, text/html, text/html;level=1, */*") to
be
given preference over an implicit quality of same rating. This is
not
honoured.
Take it for a spin, discuss your experience and please report bugs.
Lather, rinse and repeat.
Regards,
Shantanu