What we have is to put this code in our exception page
<span jwcid="@Conditional" condition="ognl:inDevel">
<span jwcid="@ExceptionDisplay" exceptions="ognl:new
org.apache.tapestry.util.exception.ExceptionAnalyzer().analyze(exception)"/>
</span>
And we put this method in the java file
public boolean getInDevel() {
return (Boolean.getBoolean("sicus_devel"));
}
As we use Tomcat (the included one in Netbeans) each developer sets the
enviroment variable
CATALINA_OPTS="-Dsicus_devel=true"
in his computer and is able to see the error report. In development we
don't have that variable so it doesn't appear.
Pedro
El Mar, 20-12-2005 a las 12:37 -0500, Dan Adams escribió:
> yeah, i know that hivemind has conditional contributions and thought
> about using that. the only thing I'm not sure of is how/where i would
> set the system properties.
>
> On Tue, 2005-12-20 at 17:57 +0100, Pedro Abelleira Seco wrote:
> > What we have done is to conditionally include the exception trace and
> > tapestry error info on it, so developers can see it and final users only
> > a "Internal error" message. I don't know if that is what you are looking
> > for.
> >
> > We used a JVM system property to do that.
> >
> > Pedro
> >
> > El Mar, 20-12-2005 a las 11:53 -0500, Dan Adams escribió:
> > > I found lots of great info on how to create a custom exception page, but
> > > I'm wondering if anyone has a good way to make the custom error page
> > > only appear in a production deploy and not in a testing deploy.
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
