Hi, How is the action processing of JSR 168 portlets being handled within Fusion? I have a struts application for which the action handling works fine within Jetspeed2 but fails with Jetspeed1.6 with fusion. (I've tried the new build from j2_deployment_sync branch that Ate has been working on). The struts application uses Lookupdispatch action for the action handling. With Fusion, somehow the method to be invoked in the action class( which is determined by the value of the "parameter" method on submit) is not invoked. With Jetspeed 2, Struts bridge seems to handle it right. So I suspect that with Fusion forwarding(handling) the action of /to the Struts bridges, somehow it seems to be missing the parameter which is required for succesfully invoking the method by Struts action classes, which it turn results in the action not being invoked. I wil try by changing the logging level to DEBUG( I believe in Fusionlog4j) . Also will try to get the logging for Struts bridges too. Anyway, If someone could give me an idea on how it is handled, it would really help me a lot.
Thanks, Hema ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Hema Menon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
