|
We arrange modules in a layout and programmatically generate
the layout into a .cfm page. We are using <cfimport> tag to call
the modules instead of <cfmodule> because <cfmodule> is slow.
Anyways, the issue at hand is how to best manage when a module produces an
error. Ideally, we would like to have the module handle this itself, but
we are dealing with a lot of pre-existing modules, so going back to each one is
time consuming and not an option. That said, what do you think about wrapping a
<cftry>/<cfcatch> around each module call within the
programmatically generated page? How costly is <cftry>/<cfcatch>
in terms of performance? Thanks - Tom Schreck 817-252-4900 [EMAIL PROTECTED] I have not failed. I've found 10,000 ways that won't
work. - Thomas Edison |
- try catch issue Schreck, Thomas (PPC)
- RE: try catch issue Nate Nielsen
- RE: try catch issue Tom Woestman
- Another Problem for new user Robert Shaw
- RE: Another Problem for new user Tom Nunamaker
