On 4/11/07, Matthias Wuttke <[EMAIL PROTECTED]> wrote:
Hi!
I am trying to use the Basic Dialog Manager. I noticed the following:
- If you only include shale-dialog (and not shale-dialog-basic) as a
dependency, you will get a NullPointerException in
DialogNavigationHandler:121. A more meaningful error message would be
helpful.
- After including shale-dialog-basic, I got a NullPointerException in
BasicDialogManager:97. It seems the dialog map is not added to the
application scope. Again, I would like to suggest providing a more
meaningful error message.
<snip/>
Please open an issue in JIRA (component "Dialog"):
http://issues.apache.org/struts/browse/SHALE
and provide recipes to reproduce these errors (some more detail on the
second one will help) and we will take a look at improving the
diagnostic messages.
- I have got a WEB-INF/dialog-config.xml file, but it does not seem to
be parsed. I resolved this to be an issue with the servlet container I
am using (Winstone) -- it does not honor the BasicLifecycleListener.
<snap/>
Yup, the container needs to honor the <listener> in the TLD packed in the jar.
I have got some questions:
- I'd like to be able to use something like <redirect/> in the
faces-config.xml navigation case definitions. Is there a way to specify
this for view transitions?
<snip/>
Sure, like so:
<view ... redirect="true">
...
</view>
See dialog-config_1_1.dtd for this, and other details. Its in the jar,
heres another pointer:
http://shale.apache.org/dtds/dialog-config_1_1.dtd
- I'd like to pass GET parameters between the dialog pages. Is it
possible to use EL expressions in the viewId attributes? Please compare
to:
http://typo.ars-subtilior.com/articles/2007/01/24/how-to-make-jsf-navigation-rules-more-dynamic
<snap/>
One approach for the basic impl could be to override getViewId() in
the ViewStateImpl (long, possibly fragmented URL):
http://svn.apache.org/repos/asf/shale/framework/trunk/shale-dialog-basic/src/main/java/org/apache/shale/dialog/basic/config/ViewStateImpl.java
to evaluate the EL expression if needed etc., and use the subclass in
your dialog-config like so:
<view ... classname="package.MyViewStateImpl">
You could still use the vanilla ViewStateImpl in other dialogs by
skipping the classname.
-Rahul
Thank you very much for this great framework!
Best regards,
Matthias
