I've contacted Toby to see what he considers the greatest changes he has
made to WW recently. Below is the list he replied with.
I have had a crack at WW-1485, which alreadt existed as WW-2294. As it
is really more of a XWork issue I have created
http://jira.opensymphony.com/browse/XW-593
I've
I just thought of something that might be an easy way to generate
XHTML views for the REST Plugin.
What if we used XSL on the client-side with the XML views? As far as
browser capabilities, I think client-side XSL could be a hidden gem
that hasn't been looked at in a while. Of course, it could
hi,
I am using 2.1.1 built from trunk and I am very happy to see how well it
works.
I found couple of really minor issues though and wanted to ask before
openning JIRA issues:
- ajax remote DIV does not work the same as in 2.0.9, there is an issue
related to the preload, updateFreq and delay
Personally, I !!HATE!! writing xsl. I try to avoid it at all costs, but
maybe others might feel differently. Is the idea here that the action
would output XML then let the xsl processor on the client convert it to
html? If so, would you expect the domain model to be automatically
serialized
Don will provide much more insight, but I thought I'd mention that the
REST plugin already automatically serializes the model as XML when an
xml response is requested (xstream).
The client can already choose to apply a transformation to that XML
response as proposed by Matt (albeit there's no
I thought I'd just add that I've been thinking along the same line as
Matt, but rather than client-side XSTL I've been desperate for a good
quality javascript templating library.
I use the REST plugin to output json results (serialized via the json
plugin) and html templates and merge them on
