In/Out takes things in and out of the various contexts (application, session, conversation and event/request).
The get/set stuff you pointed out does much the same thing but it does it on your backing bean. So the lifecycle of that variable depends on the backing bean itself. In general, I tend to use @In/@Out for entity beans and things that are in the session scope (like "currentUser"). For non-persistent things that are specific to that backing bean (like say, a verify password form input), I sometimes use get/set. In some cases, it doesn't make a difference. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3911776#3911776 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3911776 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
