I'll try 1), thanks for the help !
Randy
Weaver, Scott wrote:
>Randall,
>
>
>
>>1) Could I have the request Pull Tool move the data to the
>>session Pull
>>
>>
>
>Yes.
>
>You can retrieve ANY pull tool from the Context.
>
>Within a method in your request tool...
>
>Context context = TurbineVelocity.getContext(RunData);
>
>// "MySessionToolName" is the name you used to define the tool in
>// TR.props
>MySessionTool sTool = (MySessionTool) context.get("MySessionToolName");
>
>// Just my example, your mileage may vary.
>sTool.setFormFieldValue("SomeField",
>RunData.getParameters().getString("SomeField"));
>
>
>
>
>
>>2) Or have the request Pull Tool save the data to a
>>persistent object,
>>
>>
>
>This is another valid yet more complicated approach.
>
>If I where you and I wanted to take this approach, I would use JCS to
>accomplish it.
>
>
>
>>which I don't like since the object wouldn't be automatically cached,
>>and managed, and so forth.
>>
>>
>
>Using JCS elimnates these issues.
>
>
>I am +1 on the first approach, as it is less complicated and somewhat more
>elegant than 2.
>
>hth,
>Scott
>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
