If the tag is good enough, it'll take both start and end into consideration!
I'm trying to find a way to interface IIS and/or apache servers with a mind
reader to really let the tag do its stuff... hmmm... CF_SWAMI?
Bob Krieger
www.zyxxy.com/cf_bit
(Cold Fusion - Because It's There)
----- Original Message -----
From: "Gary Morin" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Monday, April 16, 2001 3:48 PM
Subject: RE: Error Handling
> Is that what the client wants at the start of the project or at the end of
a
> project?
>
> Gary
> -----Original Message-----
> From: Bob Krieger [mailto:[EMAIL PROTECTED]]
> Sent: 16 April 2001 22:35
> To: Fusebox
> Subject: Re: Error Handling
>
> Hey Hal,
> How much for just the CF_DWIM tag? I wanna re-write it a bit and have
> one tag that'll do what the client really wants rather what the client
> says!!! Now THAT'LL make bucks!
>
> Bob Krieger
> www.zyxxy.com/cf_bit
> (Cold Fusion - Because It's There)
> ----- Original Message -----
> From: "Hal Helms" <[EMAIL PROTECTED]>
> To: "Fusebox" <[EMAIL PROTECTED]>
> Sent: Monday, April 16, 2001 2:14 PM
> Subject: RE: Error Handling
>
>
> > You need to purchase my new "CF_Errors" tag. This amazing tag will
> transform
> > your entire development process, as YOU decide what errors you want! For
> > example, I have decided that I don't want database errors but I'm
willing
> to
> > accept missing includes so I do this:
> >
> > <cf_Errors OK="missing includes" dealWith="All others">
> >
> > Now, how much would you pay for this tag. But wait! If you act within
the
> > next 30 minutes, I'll include my special CF_DWIM tag. DWIM (short for
"Do
> > What I Mean") makes a quick end to nasty syntax problems. NOW how much
> would
> > you pay? $199 $129 $99 How about...$59 -- and I include the DWIM tag.
> Act
> > now; supplies ARE limited.
> >
> > Hal Helms
> > Team Allaire
> > [ See www.halhelms.com <http://www.halhelms.com> for info on training
> > classes ]
> >
> >
> > -----Original Message-----
> > From: Cameron Childress [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, April 16, 2001 2:39 PM
> > To: Fusebox
> > Subject: RE: Error Handling
> >
> >
> > > Gary,
> > >
> > > I usually decide upfront what kinds of errors I want... <snip>
> >
> > Me too. Hasn't been working out so well recently though... :)
> >
> > -Cameron
> >
> > --------------------
> > Cameron Childress
> > elliptIQ Inc.
> > p.770.460.7277.232
> > f.770.460.0963
> >
> > > -----Original Message-----
> > > From: Hal Helms [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, April 16, 2001 2:04 PM
> > > To: Fusebox
> > > Subject: RE: Error Handling
> > >
> > >
> > > Gary,
> > >
> > > I usually decide upfront what kinds of errors I want to be
> > > implemented from
> > > a site-wide perspective. Typically, any information sent to the
> > > user, I let
> > > bubble up to the app level and catch it there. This keeps everything
> > > uniform. Exceptions that are really speciific to the fuse or that
> > > circuit I
> > > catch there. For example, at Rooms To Go, if the credit card
processing
> > > company (RTG's private card) can't authorize a new applicant
> > > right away, we
> > > catch the exception and I put it into a table for scheduled
> reprocessing.
> > > This is the sort of exception that is specific to that particular code
> and
> > > which I would want to catch at that level. But if I wanted to
> communicate
> > > with the user over that, I would rethrow an error from within my first
> > > <cftry><cfcatch> tags. Hope that's not completely muddy...
> > >
> > > I agree with Steve about having all the error messages logged. I have
a
> > > small custom tag that writes to a text file. You could also have it
> email
> > > you, etc.
> > >
> > > Hal Helms
> > > Team Allaire
> > > [ See www.halhelms.com <http://www.halhelms.com> for info on training
> > > classes ]
> > >
> > >
> > > -----Original Message-----
> > > From: Gary Morin [mailto:[EMAIL PROTECTED]]
> > > Sent: Monday, April 16, 2001 1:06 PM
> > > To: Fusebox
> > > Subject: Error Handling
> > >
> > >
> > > Hi All
> > >
> > > I'm just about to start implementing error handling in XFB
application,
> I
> > > will probably implement code similar to Hal Helms nested error
handling
> > > code.
> > >
> > > Often errors are generated/captured in act_ pages, from the user
> > > perspective
> > > a polite message informing him of the error and requesting to do the
> > > appropriate action to correct the problem, this action may be
> > > refreshing the
> > > page, or doing a login etc. Cftry and Cfcatch will be used to handle
the
> > > errors
> > >
> > > My question is what is the excepted way to notify the problem to the
> user?
> > > In some examples, including Hal's, HTML messages are placed
> > > directly in the
> > > act file or even in the index.cfm, if the nested error handling code
is
> > > used. Or should I use an 'Error fuse' to display and error
> > > message and use
> > > a XFA to return the user to the appropriate position to continue(
> > > this would
> > > also require all variables to be passed through the error handling
> code).
> > >
> > > So how do others handle simple errors and informing users?
> > >
> > > Cheers
> > >
> > > Gary
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
