Dirk -- Taking a quick peek at both WRO4J and JAWR, I like WRO4J more. It appears to require just one servlet filter, which isn't great but isn't too bad either. JAWR requires much more configuration.
In contrast, it seems WRO4J would support a key goal: breaking the JavaScript files into chunks. For example, the AJAX "quicksearch" is used only by SearchBox.jsp. That JS code should probably go into either a classpath dir or a parallel tree hierarchy that mirrors the Java package structure. WRO4J doesn't have JAWR's the ability to inject the JS and CSS code directly into the JSP via JSP tags, but that is ok. PS. I've got some enhanced Stripes JS code done that makes the "quicksearch" feature work again, using the ActionBean URLs. It also respects ACLS. I'll check that in soon. Andrew On Sun, Feb 7, 2010 at 5:09 PM, Dirk Frederickx <[email protected]> wrote: > Currently jspwiki 'builds' its javascript and css files from ant. Building > here simply means compression by means of the YUI compressors. The sources > are large concatenations of chunks of javascript and css. > > This article ( > http://raibledesigns.com/rd/entry/javascript_and_css_concatenation) showed > me some light-weight, alternative approach for building the js/css > on-the-fly, with some additional features as bonus. > > It will allow to break the js into logical chunks, and improve source > management. The same can be applied to the css file. > > See project home page at http://code.google.com/p/wro4j/ > > > WDYT ? > > dirk >
