Is configType a parameter? where is it coming from?
musachy
On Fri, Oct 3, 2008 at 10:16 AM, Giovanni Azua <[EMAIL PROTECTED]> wrote:
> hi,
>
> I have different types of (trading strategy/algorithm) configurations. My
> application allows scheduling Simulations for any of the existing types,
> depending on the type it should be redirected to a specific form e.g.
>
> --------------------------------------------
> Example
> --------------------------------------------
> Algo 1 Config -\ / Form Schedule Sim "Algo 1 Config"
> Algo 2 Config -- Opp -> Fork - Form Schedule Sim "Algo 2 Config"
> Algo 3 Config -/ \ Form Schedule Sim "Algo 3 Config"
>
> I have many "Opp" actions that generically handle any type of configuration
> but from there it needs to redirect to the type-specific form. To do the
> forking part I am trying to use a redirect action mapping with an OGNL
> expression like this:
>
> <action name="FormScheduleSimulation">
> <result type="redirectAction">${ 'FormScheduleSimulation' +
> configType.name }</result>
> </action>
> But here the result parameters coming from "Opp" do not get passed through
> and the ONGL expression does not see the needed configType bean. To solve
> this I imported the CodeBehind plugin expecting it to automatically discover
> that "FormScheduleSimulation" action does not have a corresponding Action
> class and therefore it would create one on the fly and let the original
> action result parameters pass right through including the needed
> "configType" but does not work.
>
> Is there any additional step to take for the Code Behind plugin to work
> here ... ?
>
> TIA,
> Regards,
> Giovanni
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
"Hey you! Would you help me to carry the stone?" Pink Floyd
