Thanks Simeon. I agree with you that the best practice should be calling an action fuse from the model circuit but there are some cases where it would be easier just putting it in the circuit itself.

On 8/15/06, Simeon Bateman <[EMAIL PROTECTED]> wrote:
Well again, I cant honestly advocate this as a best practice, its just how I do it most times :)

<set name="member" value="#application.recordFactory.createRecord('member').load(memberid=5)#" />

But something like that will return a member record of the  member with id = 5.  But the same thing could go for a gateway call.  Something like:

<set name="memq" value="#application.recordFactory.createGateway('member').getAll()#" />

And that would be based on you having initialized your reactor record factory and stored it in the application scope as recordFactory.  And the standard best practice I believe is to have your model circuit include act_ files that are appropriately named.  That way you can change the behaviour as you wish without having to muck up your xml.

HTH,

Simeon


On 8/15/06, Ray Buechler < [EMAIL PROTECTED]> wrote:
Simeon,

Could you give a quick example of how you do your set calls in your model circuit? I tried a while back and couldn't get it to work so I just started putting the Reactor calls into fuses.

Thanks,

Ray



-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Reactor for ColdFusion Mailing List
[email protected]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Reactor for ColdFusion Mailing List
[email protected]
Archives at: http://www.mail-archive.com/reactor%40doughughes.net/
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

Reply via email to