RE: fix for moving legacy code to application.cfc w/ local variab les

2005-06-03 Thread Calvin Ward
, 2005 12:10 AM To: CF-Talk Subject: Re: fix for moving legacy code to application.cfc w/ local variab les On 6/2/05, Dave Watts [EMAIL PROTECTED] wrote: No, don't use OnRequest - that will replace the page that was actually requested. You could use OnRequestStart, or just put them in the pseudo

RE: fix for moving legacy code to application.cfc w/ local variab les

2005-06-03 Thread Isaac Dealey
First, what's wrong with setting local variables in Application.cfm? I don't like the (potential) scoping implications of it... local variables set in the application.cfm, particularly for some of the most common variables that are set this way (dsn/datasource for instance) are then not

RE: fix for moving legacy code to application.cfc w/ local variab les

2005-06-03 Thread Dave Watts
First, what's wrong with setting local variables in Application.cfm? I don't like the (potential) scoping implications of it... local variables set in the application.cfm, particularly for some of the most common variables that are set this way (dsn/datasource for instance) are then not

Re: fix for moving legacy code to application.cfc w/ local variab les

2005-06-03 Thread Sean Corfield
On 6/3/05, Calvin Ward [EMAIL PROTECTED] wrote: How would you recommend working around the remoting/gateway issue? Simply by not using OnRequest (which impacts the ability to use OnError), or would you have a different solution? I would use a different Application.cfc and have the web services

Re: fix for moving legacy code to application.cfc w/ local variab les

2005-06-03 Thread Calvin Ward
That certainly makes sense. I recall seeing something about needing to use onRequest to leverage onError in a certain fashion, but I'll be darned if I can remember where I saw that... - Calvin On 6/3/05 10:20 AM, Sean Corfield [EMAIL PROTECTED] wrote: On 6/3/05, Calvin Ward [EMAIL

Re: fix for moving legacy code to application.cfc w/ local variab les

2005-06-03 Thread Raymond Camden
It would be nice if, in the future, FR/WS calls simply didn't try to run onRequest. On 6/3/05, Sean Corfield [EMAIL PROTECTED] wrote: On 6/3/05, Calvin Ward [EMAIL PROTECTED] wrote: Note that the primary reason for using onRequest() is to set variables scope data that is accessible in your

RE: fix for moving legacy code to application.cfc w/ local variab les

2005-06-02 Thread Dave Watts
I'm betting the answer to this is no, but has anyone found a way of migrating an existing application.cfm to the onRequestStart portion of an Application.cfc while maintaining the viability of local variables that had been set in the Application.cfm? I know it's a bad practice -- wasn't my

RE: fix for moving legacy code to application.cfc w/ local variab les

2005-06-02 Thread Dave Watts
I think you can use the OnRequest method (be sure to read up on it) and anything declared there will be fine as local variables just like Application.cfm. No, don't use OnRequest - that will replace the page that was actually requested. You could use OnRequestStart, or just put them in the

Re: fix for moving legacy code to application.cfc w/ local variab les

2005-06-02 Thread Sean Corfield
On 6/2/05, Dave Watts [EMAIL PROTECTED] wrote: No, don't use OnRequest - that will replace the page that was actually requested. You could use OnRequestStart, or just put them in the pseudo-constructor area I think. No, if you want page-local variables to be accessible in the requested page,