I did something like this in my application's default layout, although
the only thing it dumps is the parameters. The feature is turned on
or off in the properties file as you suggest.
Right now my implementation is dependent on the XMLC/Turbine
integration that I did for my current project, so the code wouldn't
be useful to anyone yet. I'm still planning on reworking the XMLC
integration and officially submitting it to the Turbine project, as soon
as I get out from under my current heavy workload...
In any case, I've found the feature to be very helpful, and it would be
a nice addition to Turbine.
-Jon
----- Original Message -----
From: "Nissim Karpenstein" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, October 18, 2000 9:53 AM
Subject: Debug features of Cold Fusion
> Hi all,
>
> I used to work with cold fusion (which sucks big time), and it has a
really
> cool feature which I think we could integrate into Turbine. You can turn
on
> debugging, and every page that the Cold Fusion server generates, it will
> append all of the parameters, and session variables, and http headers to
the
> end of the generated html. It's very helpful, because you can see the
data
> that the server had right on the page you're testing.
>
> I think we could add it into the Turbine servlet right before we output
the
> page, we can generate the debug information, and append it to the body if
> some debugging parameter in TR.props is set to true.
>
> Does this sound like a good idea?
>
> -Nissim
>
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
