A lot of frameworks are building off of simple Annotations or dynamic invocation, basically extensions per Class instance. To avoid re-mining this data, we attempt to cache it. This works fine, except when we deal with hot deploys or restarts with statically scoped caches. Keeping reference to some classes/ClassLoaders after repeated restarts could quickly gobble resources.
StateSaving in JSF is the uncle no one wants to talk about. You get a lot of things for 'free' with JSF, but for the most part, these features end up adversely affecting the state size of the view.
Part of Avatar for JSF was being able to make a single, lightweight request to the Server and actually receive multiple elements at once in a single HTTP Response. An example would be a single button that would force re-rendering of 5 different parts of the page with one AJAX request.
Facelets 1.1.12 was just uploaded to Java.net and includes many small bug fixes for JSF 1.1 (MyFaces 1.1.4) and JSF 1.2 (RI 1.2_03b5).
I've been working a bit on extending EL, but found that the API is missing a few features desired to fully make the language pluggable by third parties.
I use Eclipse both at home and at work, but finally decided to give NetBeans a spin. Overall, the IDE is solid, but some of the features seem too 'literal'. For lack of a better word, let me use an example instead. When I'm writing test cases, I'll constantly comment and uncomment lines. Instead of providing one comment toggle control, NetBeans has two different ones:
Updated 11/17/2006 with JEXL and upgraded MVEL and added Serialized size
I decided to test the following EL libraries available today:
JavaOne was fantastic this year. Being a presenter did put a very different twist on the week-- especially going at the end. This left Ed Burns, Adam Winer, and I plenty of time to go over our presentation. I might as well been tied at the hip with them because of all our practices dotted throughout my session schedule.