Hi,
 
I am using Struts Bridge to deploy a big struts application as a portlet and I 
must face several problems. 
I noticed that the main difficulties come from the fact that a single struts 
request is devided in two ; ActionRequest 
and RenderRequest. 
But the way it is done in Struts Bridge does not worj properly in case of 
action chaining. 
Indeed Struts Bridge ends the ActionRequest at the first forward. So the first 
action forwards toward another action 
the second action  will be processed into the RenderRequest and, due to the 
nature of the RendeRequest, the request parameters 
are lost. 
 
I have read in a previous thread that 
"action chaining isn't really supported nor a recommended way of
using Struts by the Struts guru's themselves.
" but my application is largely based on that so I must make it work. However I 
personnaly think that not beeing able to use action chaining is a serious 
limitation. 
 
To deal with that problem I had to write a mechanism to save request parameters 
just before the first forward, so they still 
can be readen in the renderRequest. 
 
I wonder if it's normal to do so, or if  I mised something in my understanding 
of Struts Bridge. 
 
Another problem is that man must list every attributes that should be 
transfered from ActionRequest to renderRequest. Is there a way to save and 
restore 
every attributes without having to explicitly declare them in a configuration 
file ?
 
 
-------

Rémi Cocula
Division immobilier - R&D ULIS
Sopra Group
Tel. : +33 (0)4 72 18 47 13 - Fax : +33 (0)4 72 18 48 01
email : [EMAIL PROTECTED]

 

Reply via email to