correcty i user the basic impl.
the logical outcome return as string for example "edit"
1-i understood the Dialog in such a way that my alist is as long as the
dialog do not reach the End State i can access the DialogScope
2- i do not need to use the Subdialog my Question is: how kann i use the SI
for clarity, the scenario:
1.<h:inputText id="username" value="#{dialogScope.user}">
2. DialogContext dcontext = DialogHelper.getDialogContext(context);
appBackingBean currentuser = (appBackingBean) dcontext.getData();
do some work with currentuser
return logical outcome and deliver the "alist"
3. <t:dataTable var="result" value="#{dialogScope.alist}"....>
4. edit the value="#{dialogScope.alist}
note that the "alist" depends on "ontherBackingBean" wich will take another
work to reach the finale state of the "alist" to store in DB.
i can`t let the connection between ontherBackingBean and appBackingBean
works.
Sam
Rahul Akolkar wrote:
>
> 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!!
>>
> <snip/>
>
> Couple of perhaps related clarifications, based on my understanding of
> this scenario:
>
> * A subdialog is entered via a <subdialog> state (in the basic impl),
> rather than by providing a logical outcome / action matching
> "dialog:subdialogname"
>
> * The default prefix is "dialog:" and prefixes are case sensitive.
>
> -Rahul
>
>
--
View this message in context:
http://www.nabble.com/transition-between-2-Dialog-tf3885103.html#a11015153
Sent from the Shale - User mailing list archive at Nabble.com.
