Pushing the envelope

While playing with Webwork and the JMX-RI it occurred to me to wonder what webwork would look like if it was JMX-ified.  If the action mappings were exposed as managed properties, would it be possible to re-configure the workflow of your webapp on the fly via a browser?  Hmm.  That could be fun.  What about using JMX notifications to make WW reconfigure itself in response to network events?  (Like putting a 'we're sorry' message over a bit of the app. if a db goes down, then automagically re-enabling it when it's back up).  Is this even remotely possible we ask?

If nothing else attempting to find out should improve my understanding of both WW and JMX.

Eclipse - thought I'd give it bit more of a test drive. Its been fine, apart from its wierd insistence that non-project source files have to be in jars. Why can't I just point it at a directory? And its hugely annoying that you can't apparently specify a project source code directory outside of your project path. My opinion currently is that the SWT widgets make it look nicer than IDEA, but it has a way to go in ease of use terms. Oh yeah, and it deleted a whole bunch of property files in my classes directory without telling me it would, which was nice.

Webwork - A bit fiddly to get started with. The skeleton app didn't work initially, it was looking for an 'xhtml' directory that wasn't there. I eventually found it in the examples folder, and copied it to the webapp, whereupon it worked fine. From what I've seen so far in my dabbles it looks like there is a lot of good stuff here though.