On Sun, 2007-01-21 at 14:20 -0800, Craig McClanahan wrote: Thanks. I got it.
> On 1/21/07, Duong BaTien <[EMAIL PROTECTED]> wrote: > > > > Hello Craig: > > Thank for a quick response. I downloaded the 1.1.0-SNAPSHOT but cannot > > find a binary for trunk/shale-apps/*. > > > Each individual application is packaged and uploaded separately. The test > apps are in [1]. > > > Do you think it will be available > > soon? What is the difference between shale-apps and shale-application > > directories? > > > The "shale-application" module is the Application Controller[2]. The > "shale-apps" module is the parent pom for all of the example and test > applications, containing shared stuff so it does not have to be repeated in > the pom for each individual application. > > Craig > > [1] http://people.apache.org/builds/shale/nightly/tests/ > [2] http://shale.apache.org/shale-application/index.html > > > On Sat, 2007-01-20 at 17:43 -0800, Craig McClanahan wrote: > > > On 1/20/07, Duong BaTien < [EMAIL PROTECTED]> wrote: > > > > > > > > Hello Craig: > > > > > > > > I am trying to look at shale-apps/shale-test-view to see an example of > > > > ViewController exception handling. I download from svn and try to > > build > > > > it from mvn but get the following exception: > > > > > > > > The plugin 'org.codehaus.mojo:cobertura-maven-plugin' does not exist > > or > > > > no valid version could be found > > > > > > > > I then try to get the latest nightly build, but they all disappeared. > > > > Where are they located now? > > > > > > > > > There has been a glitch on the server that creates the nightly builds, > > which > > > I just fixed. We should see tonight's (and following) builds appear in > > the > > > usual place[1]. > > > > > > Craig > > > > > > [1] http://people.apache.org/builds/shale/nightly/ > > > > > > > > > Thanks > > > > BaTien > > > > > > > > > > > > On Fri, 2007-01-19 at 14:47 -0800, Craig McClanahan wrote: > > > > > On 1/19/07, Reynolds, James < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > > I have a question about the org.apache.shale.view.ExceptionHandler > > > > > > interface. Comments in the Shale Wiki indicate that Shale "...can > > > > > > > > optionally do a RequestDispatcher.forward() call to the context > > > > relative > > > > > > path of an error display page..." How do I invoke the option to > > > > forward > > > > > > to my error page? > > > > > > > > > > > > I've created my ExceptionHandler class (code below) and configured > > it > > > > > > successfully. I also configured this parameter in my web.xml: > > > > > > > > > > > > <context-param> > > > > > > > > > > > > <param-name>org.apache.shale.view.EXCEPTION_DISPATCH_PATH > > </param-name> > > > > > > <param-value>/exceptionViewer.jsf</param-value> > > > > > > </context-param> > > > > > > > > > > > > ExceptionHandler code: > > > > > > > > > > > > public class WebEnabledExceptionHandler implements > > ExceptionHandler { > > > > > > > > > > > > public WebEnabledExceptionHandler(){ > > > > > > } > > > > > > > > > > > > public void handleException(Exception exception) { > > > > > > System.out.println("Shale ExceptionHandler: " + > > > > > > exception.getMessage()); > > > > > > // How do I forward to the error page? > > > > > > } > > > > > > } > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > It's magic :-). > > > > > > > > > > Actually, the act of declaring the forward path (as you are doing > > here) > > > > > enables the forwarding automatically. The code that actually does > > this > > > > is > > > > > the afterPhaseExceptionCheck() method in ViewPhaseListener, which is > > > > called > > > > > at the end of each phase. IF any exceptions have been queued up, > > AND > > > > the > > > > > web.xml declares a forwarding path, THEN it will do the > > forwarding. You > > > > do > > > > > not need to provide a custom ExceptionHandler to accomplish this. > > > > > > > > > > Craig > > > > > > > > > > > > > > > E-Mail messages may contain viruses, worms, or other malicious code. > > By > > > > > > reading the message and opening any attachments, the recipient > > accepts > > > > full > > > > > > responsibility for taking protective action against such code. > > Sender > > > > is not > > > > > > liable for any loss or damage arising from this message. > > > > > > > > > > > > The information in this e-mail is confidential and may be legally > > > > > > privileged. It is intended solely for the addressee(s). Access to > > this > > > > > > e-mail by anyone else is unauthorized. > > > > > > > > > > > > > > > > > > > > > > > >