OK fine on the robustness front - I off-handedly said robustness because
I normally equate less code with robuster code. But don't let's bother
discussing that.
So what you are saying is that really all you need to do to implement
this feature is to keep the struts mapping the same and put no-cache
instructions in the page header.
I can do that anyway without using DialogAction, right? Unfortunately
your further discussion lost me since I only have a vague concept of
what the terms web control and portlet actually mean.
Adam
On 09/06/05 17:53 Michael Jouravlev wrote:
On the other hand, if you use any version of Netscape starting from
4.x, (yes, Netscape 4 works great), Mozilla/Firefox or Internet
Explorer (I could not find IE4 for testing), then your users get
immediate benefits in user experience and in overall application feel.
And, you cannot create what I call a "web control" without redirection
and two-phase I/O processing. Think of DialogAction, especially when
you creating a control out of it, as of very simplified portlet. But
portlets has a specific API, like doDispatch() or doView().
DialogAction does not have API, simple reload works as doView(). It is
a actually a big thing, and ability to create a web control allows to
have a simple portal without portlet container. You just drop an URL
to master page, and you do not care about anything else. Whenever
master page is reloaded, the control is reloaded too, and it displays
content, reflecting current control state.
About simplicity. Funny that you mentioned this, because creating a
dialog using DialogAction is simple, just use your form bean fields,
or use a nested business object within a form bean with session scope,
and you get event model, storage for your dialog data, and message
handling.
It might be not a big deal for you, if you do not play with browser
buttons like a kid. If you do not feel like clicking Refresh just
because of fun of it, or clicking Back just to check what happened to
previous page, if you are not annoyed by POSTDATA messages, then you
might not appreciate what DialogAction does. But for me POSTDATA
dialogs are infuriating, I simply hate them.
And, if the above did not convince you: Ruby On Rails adopted the same
two-phase approach to I/O forms. JSF provides the same features, if
you look at JSF samples, all backing beans are defined with session
scope, you just need to put <redirect> tag in config file. Spring MVC
has similar features with RedirectView class.
The DialogAction may not be perfect (yet), and may need some
improvements, but it works and it is pretty stable. I will be glad
hearing about possible updates and changes.
Michael.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
