Lincoln, your suggestions would be a valid workaround, but it would also increase memory requirements and cause cache update considerations for things which should really just be request based... This would also require all FBs of our site to change scope because of possible common include with commandLink (not very scalable IMHO putting the burden on the rest of the webapp). I was hoping for a less tightly-coupled solution where our commandLink could act in such a way as to not disrupt other beans on the page?
[Message sent by forum member 'bouteill' (bouteill)]
http://forums.java.net/jive/thread.jspa?messageID=342099