On 6/7/07, samju <[EMAIL PROTECTED]> wrote:
to resume i have Login.java and two Beans A and B wich are mapped with Hibernate 1-<dialog name="login" start="activateLog" dataClassName=xxx.BBean> 2-Login class extends AbstractViewController this class provide a login Action that return the "alist" other statements omitted 3-<t:dataTable var="result" value="#{dialogScope.alist}"....> ..... <t:inputText value="#{result.sname}"> ..... <t:commandButton action="#{login.transferToEdit}" value="update"/> </t:dataTable> the action="#{login.transferToEdit}" had to push "Dialog:edit" need the BBean to update the ABean 4-<dialog name="edit" start="activateEdit" dataClassName=xxx.ABean> the action="'{edit.updateAlist}" will update the DB entries. i tried the subdialog didnĀ“t work! how to solve this? Setter Injection or DI ? any hints .. if someone had time i will provide more details!!
This sounds like it might be the same sort of issue Mario is having with the data bean in subdialogs, but it depends on what "the subdialog didn't work" means. Could you describe what you expected, and what you observed, in a little more detail? Craig
-- View this message in context: http://www.nabble.com/transition-between-2-Dialog-tf3885103.html#a11012245 Sent from the Shale - User mailing list archive at Nabble.com.