Hi, If seperating these UI concerns from the business logic is a great concern, there is no reason you can't have a more traditional stateless service layer that your Seam EJBs talk to, and which could then be used by other clients. You'll need to get your persistence context strategy right, so that your Seam-managed PC propagates into the next layer (if you want that), but it's definitely possible. Remember though that other non-Seam clients of this service layer won't have a Seam-managed PC and will need everything fully populated if you want to avoid lazy initialisation exceptions and the like. Daniel. "hsiung" wrote : Hi Pete | | I don't understand how to avoid using UI elements like ValueChangeEvent when using SelectOneRadio. | Or simply how to use SelectOneRadio in a table without using UI information on the EJB container. | I just want to select a row (I think SelectOneRadio is apropriate) and then choose an action (press a button). On the SFSB the action should know which row has been selected. | | Thanks for your help | Alain View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047076#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...