thx.  I guess that's the way I'll have to do it.

I had thought that application scope was working, when I only had one app defined, but clearly it was using the Default application definition.

So does anyone have application scope working?


On Monday, February 28, 2005, at 05:21 AM, Robert Shubert wrote:

Bill, since I don't support/use application scope myself, I can't be of
much help with your problem directly, however I solve your problem by
essentially putting logic in my error file that looks at @DOMAIN to
determine what to do. You could just as easily look at @APPFILEPATH to
change the effect of your error file much like using the path of the
application scope.

Robert

-----Original Message-----
From: Bill Conlon [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 27, 2005 4:44 PM
To: Witango-Talk
Cc: [EMAIL PROTECTED]
Subject: Witango-Talk: Still baffled by application scope

I am having a devil of a time defining applications in
applications.ini.  It seems that I only can get the Default application
(PATH=/) to work.

If I run a simple taf to print <@APPNAME><@APPPATH>, I will always get
"Default/" no matter if the appfile is within an application path.

Interestingly, if I change the default path to point to my application
web root

[Default]
PATH=/path/to/web/root

then <@APPNAME><@APPPATH> is empty, just as if application scope was
off.

Anyone have any suggestions?

BTW, using domain scope isn't an option, because I'm actually trying
set defaulterrorfile.  This cannot be done in domain scope.

thx.


_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf


_______________________________________________________________________ _
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf



________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf

Reply via email to