The error page usually gets seen in development mode most of the time,
and there lies its greatest strength. The first phase of an
application in its life cycle is also development, and most people
trying out Wicket will /want/ to see a good debugging tool. Tapestry
is touting its line precise error reporting for their 4.0 release, we
have that since 1.0, and it is getting better every release. I want to
show that!
+1 on default development mode, and mind if I add: let's create a
couple of error pages in our wicket examples project to showcase our
reporting. It would also be useful for future changes (J[web]Unit
test) when the errorreporting goes wrong...
Martijn
On 1/20/06, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
> +1 to have development as the default.
>
> If you don't want to change web.xml, make the setting deployment your default
> ;)
>
> Eelco
>
> On 1/20/06, Johan Compagner <[EMAIL PROTECTED]> wrote:
> > I don't want to change web.xml because i am suddenly deploying.. Then you
> > have to do special things
> > by building the web.xml or getting it from another tree.
> > I prefer that i don't have to change anything.
> > Ofcourse this is possible by adding the context param to deployment by
> > default and then override it again.
> >
> > So change it to development by default?
> >
> > johan
> >
> >
> >
> > On 1/20/06, Juergen Donnerstag <[EMAIL PROTECTED] > wrote:
> > > IMO development should be default. By means of <context-param> in your
> > > web.xml all apps can be switched to deployment. The system parameter
> > > could replace whatever has been configured in init-param or
> > > context-param. I think that is ok.
> > >
> > > Juergen
> > >
> > > On 1/20/06, Johan Compagner < [EMAIL PROTECTED]> wrote:
> > > > I think this is because of the current change in the configuration.
> > > > The default is now deployment because you can use a System property:
> > > >
> > > > String configuration = System.getProperty("wicket." +
> > > > Application.CONFIGURATION );
> > > >
> > > > // If no system parameter check servlet specific <init-param>
> > > > if (configuration == null)
> > > > {
> > > > configuration =
> > > > wicketServlet.getInitParameter(Application.CONFIGURATION );
> > > > }
> > > > // If no system parameter and not <init-param>, than check
> > > > <context-param>
> > > > if (configuration == null)
> > > > {
> > > > configuration = wicketServlet.getServletContext
> > > > ().getInitParameter(Application.CONFIGURATION);
> > > > }
> > > >
> > > > // Deployment mode is default if not settings have been found
> > > > if (configuration != null)
> > > > {
> > > > configure(configuration,
> > > > wicketServlet.getInitParameter ("sourceFolder"));
> > > > }
> > > > else
> > > > {
> > > > configure(Application.DEPLOYMENT,
> > > > wicketServlet.getInitParameter("sourceFolder"));
> > > > }
> > > >
> > > > So you don't have to configure anything for deployment and if you
> > develop
> > > > then you can say that with a
> > > > system property so no configuration files needs to be updated for a WAR
> > > > build.
> > > >
> > > > If we make the default development then the system property doesn't make
> > > > much sense i am affraid
> > > > because setting a system property for deployment is a bit strange.
> > > >
> > > > johan
> > > >
> > > >
> > > >
> > > > On 1/20/06, Igor Vaynberg < [EMAIL PROTECTED]> wrote:
> > > > > whenever there is an exception i always get the internal error page
> > now
> > > > instead of the exception page.
> > > > >
> > > > > -Igor
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> > files
> > > for problems? Stop! Download the new AJAX search engine that makes
> > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> > >
> > http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
> > > _______________________________________________
> > > Wicket-develop mailing list
> > > Wicket-develop@lists.sourceforge.net
> > >
> > https://lists.sourceforge.net/lists/listinfo/wicket-develop
> > >
> >
> >
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid3432&bid#0486&dat1642
> _______________________________________________
> Wicket-develop mailing list
> Wicket-develop@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-develop
>
--
Living a wicket life...
Martijn Dashorst - http://www.jroller.com/page/dashorst
Wicket 1.1 is out: http://wicket.sourceforge.net/wicket-1.1
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
