brittm, i think that method binding *is* supported in our current implementation. i remember i tweaked commons-el to check for property-getters, fields and methods. but the downside is that this feature might be removed as we are probably going to standardize on the jboss-el implementation. that one supports even parameter binding in methods, but you have to choose wether you do a value binding or a method binding upfront. which means that you'll have to use different tags for method binding as for value binding in the language. for adding the ui-stuff like confirm="true" to the process, i'm not that strict in separating process and UI things. i believe there can be some overlap for convenience. however we are very careful before we implement things that we don't consider crucial. as every piece of code that we include requires maintenance. and if this maintenance becomes too big for the benefits, combined with the load we can handle, it might be that your feature just gets removed. that is worse for you. so we are very reluctant to adopt new features, not in the core target of the project and if there is a chance that we might not be able to sustain the maintenance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4053806#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...