Hi Ate,
Thanks for the feedback, see below for my answers.
Ate Douma wrote:
Unfortunately for regular servlets this is not possible, as we don't necessarily have a two-phase process (controller -> view). If one wanted, they could do everything with just a JSP, or just a servlet, and it would still have to work.
Well, how are you going to process posted data? In a portlet you *have*
to process these during ActionRequest because the parameters will be lost
in the RenderRequest. Whatever way you look at it, you will have to split
the controller and view for that. I never looked deeply into the PHP/Perl
portlet bridges but I'm wondering how it is solved there if they neither
use the ActionRequest.
One possible (but ugly) solution might be capturing all ActionRequest
parameters and store them in the PortletSession and restore them in the
next RenderRequest. I've provided something of that kind (but then for
saving ActionRequest Attributes) in the Struts bridge which can be
configured through the struts-portlet-config.xml. Maybe that feature of the
Struts bridge can be of use to your proposed bridge...
Strange... What I did was use only render URLs for POST methods, and it seems to work. I realize this is not the "official" way of doing things but is this wrong ? I seem to also be able to retrieve all the parameter on the RenderRequest method this way. I haven't tested with multipart/form-data yet though.
If this is not a recommended way, maybe I'll go the session way with ActionURLs/ActionRequests since Roger seems to have used this method too.
Regards, Serge Huber.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
