We already have a custom portal, and navigation to the default URI (something like http://server/portal) goes directly to our login screen.  But once logged in, entering an invalid URL in the browser's address line will forward to the JBoss Portal.  We want 404 errors to go to our custom portal's default page, not to JBoss.

Is it possible that something was not defined properly, and our portal isn't really the "default"?  I was not the initial developer, so I'm not sure what to check to verify it.  I do know that the method of redirecting to our login page is done by adding (or modifying) the login-config element to the jboss-portal.sar/portal-server.war/WEB-INF/web.xml.

Kevin

Thanks, Peter.  Your presentation looks extremely helpful, but it's very likely that our custom portal was originally done completely wrong -- I'm not sure there was any clear direction on how to do it when we started.  I hope it's not too much trouble to do it the right way.

Our portal definition is in its own EAR with the xxx-object.xml not named "default-object.xml".  Portlets are deployed within their own EAR or WAR files, allowing for third-party development of future portlets.  There are modifications, as mentioned previously, to the jboss-portal.sar/portal-server.war/WEB-INF/web.xml such as definitions of login-related servlets and the login form info.

This doesn't sound anything like what you describe in your presentation.

Kevin