shale-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SHALE-454) extending AbstractDialogContextListener getDialogContext().getName() returns null in onStart() method
Date Tue, 03 Jul 2007 21:51:27 GMT

    [ https://issues.apache.org/struts/browse/SHALE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_41341
] 

Rahul Akolkar commented on SHALE-454:
-------------------------------------

The reason is similar. I think you may have posted a simplified snippet, otherwise its possible
to set the dialog data in the dialog descriptor itself, rather than using the approach above.

In any case, in the above scenario, I'd recommend using onStart() for making sure all resources
are available for the instantiation of dialog data, but actually instantiating (and configuring)
it in onActivate().

As an aside, at first glance, I suspect a single onEntry() callback might be escaping out
before the onActivate() call, and I intend to take a better look at that later in the week.


> extending AbstractDialogContextListener getDialogContext().getName() returns null in
onStart() method
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SHALE-454
>                 URL: https://issues.apache.org/struts/browse/SHALE-454
>             Project: Shale
>          Issue Type: Bug
>          Components: Dialog
>    Affects Versions: 1.1.0-SNAPSHOT
>            Reporter: mario buonopane
>
> i'm using Shale Basic Dialog 1.1.0 and I have a my DialogContextListener extending AbstractDialogContextListener.
In onStart() and onStop() methods, getDialogContext().getName() returns null.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message