Greetings! I just recently discovered wicket and have been playing around with it. I'm impressed so far, it seems to be just what I was looking for.
I've also been playing around with apache/jakarta commons vfs module (just released 1.0 this past December), which provides i/o access to files within a zip/tar/jar. There are several programs I've seen in Linux that use a tar file to contain theme information (graphics, stylesheets, etc), and read files from the tar directly. So it seems to me a rather natural fit from a deployment perspective to actually separate the HTML, CSS, and graphics out into another module. So you could change the UI at any time without re-deploying your application, and you wouldn't have to be bothered with expanding or deploying anything extra. In case you're wondering, the VFS module handles caching of extracted content, but in general using 0 compression works the best. In thinking this through, one of the issues I can see with this is that the UI archive, if it contains css/javascript/html, etc. that isn't handled by wicket, will need to have some other java based interface to get at it (a getFile servlet or something). Now, I know, you're probably better off in most situations performance wise having a separate web server handle pushing your static content, but having it all in one easily deployable package is very attractive too. Thoughts? Thanks, Mark ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
