1 Reply Latest reply on Aug 24, 2007 11:41 AM by bvogt

    How to handle portal specific PageNotFound situation

    bvogt

      AS 4.0.5, Portal 2.4.1:

      When using a custom portal with a custom theme calling an invalid portal page causes the portal to switch to the 'default' tab/page of the default portal.

      Is it possible to intercept this processing to display a custom portal page?

      Thanks for any hints in advance.

        • 1. Re: How to handle portal specific PageNotFound situation
          bvogt

          looking at the sources I would do:

          1. extend org.jboss.portal.core.model.portal.DefaultPortalCommandFactory
          2. define 1. as mbean in jboss-service.xml of portal-core-sar similar to DefaultPortalCommandFactory but a different name and
          3. reference the name of 2. as CommandFactory of mbean org.jboss.portal.core.CoreController
          4. re-compile the sources.

          That seems to work, but is there an opportunity to do this on a declarative basis, i.e. not re-compiling the portals sources?

          Thanks for any hints in advance (I know there's a lot to do in 2.6...)