well I have to dig into this a bit more, cause the actual integration test for pax-web don't seem to have an issue with this. I'll try to fix this with 2.0 better :) If you have more information that could be helpful please add those in the corresponding jira entry.
regards, Achim 2012/3/8 Raman Gupta <[email protected]>: > Actually, as per the bug report, this applies even to the first WAB > when using the error-code element rather than exception-type. > > Is there a work-around for this short of generating the error page > from directly within the app? > > Regards, > Raman > > > On 03/07/2012 02:59 PM, Achim Nierbeck wrote: >> Hi >> >> there is an issue for this at pax-web >> >> https://team.ops4j.org/browse/PAXWEB-341 >> >> but this is about a second wab registering a custom error page. >> >> >> regards, Achim >> >> Am 07.03.2012 19:08, schrieb dleblanc: >>> Hello, has there been any progress on this issue? We're seeing the >>> same thing >>> in our deployment. Is there a Jira we could follow for this? (I >>> didn't see >>> one). >>> >>> Thanks, >>> >>> -Dave >>> >>> -- >>> View this message in context: >>> http://karaf.922171.n3.nabble.com/Custom-error-page-in-web-xml-not-working-tp3607253p3807464.html >>> >>> Sent from the Karaf - User mailing list archive at Nabble.com. >> >> -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/>
