Hi,
java.io.FileNotFoundException: /gov.usdoj.afms.esp.modules.login.LoginPage
at
com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(
DefaultExtensionProcessor.java:572)
at
com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3933)
is an exception coming from you web container.
There is nothing Wicket related in it.
If the markup cannot be found then I'd expect to see Wicket's
MarkupNotFoundException.
Where /gov.usdoj.afms.esp.modules.login.LoginPage comes from ?
Is this a mount path defined by you in YourApp#init() method, via
#mountPage() ?
Or maybe this url is missing the leading /wicket/bookmarkable prefix that
WIcket uses for all pages which are not explicitly mounted.
Can you put a breakpoint at DefaultExtensionProcessor.handleRequest(
DefaultExtensionProcessor.java:572) and see what happens ?
It seems WicketFilter doesn't recognize this url and lets the web container
default handler to try it, and it fails.
On Thu, Dec 12, 2013 at 3:52 PM, Entropy <[email protected]> wrote:
> So, the app worked before I made my 1.4.7 -> 6.12 changes. The general
> flow
> is that when I hit the URL for the app (with no parameters...that 404 URL
> is
> not something I typed from the browser) it goes to the
> Application.getHomePage(), which returns the home page (not the login
> page).
>
> We have a common block in all our pages that check if the user has
> authenticated, and if not, forwards to the login page like so:
>
> throw new RestartResponseAtInterceptPageException(getLoginPageClass());
>
> And then I can see the control enter my LoginPage class. So it found the
> java. I walk through the LoginPage initialization. Nothing blows up,
> everything looks kosher. Then after control returns to the wicket layer
> above me, it evidently can't find something...I presume the HTML since it
> already found the java, and I get the exception I mentioned. And not my
> custom error page.
>
> I set my error page up like:
>
> IApplicationSettings settings = getApplicationSettings();
> settings.setInternalErrorPage(ESPApplicationErrorPage.class);
>
>
> getExceptionSettings().setUnexpectedExceptionDisplay(IExceptionSettings.SHOW_INTERNAL_ERROR_PAGE);
>
> and that block runs, but no code in the error page is ever reached.
>
> I don't understand how the java can be found and not the HTML for the
> LoginPage when 1.4.7 found them fine, and the HTML is in the same package
> as
> the java, just like before. And unfortunately, the error really doesn't
> give me alot to go on.
>
>
>
> --
> View this message in context:
> http://apache-wicket.1842946.n4.nabble.com/Converting-1-4-7-to-6-12-Login-Error-tp4662916p4662954.html
> Sent from the Users forum mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>