[
https://issues.apache.org/jira/browse/FELIX-4548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Baier updated FELIX-4548:
--------------------------------
Attachment: felix-4548-exception-hierarchy.patch
There are two things still missing in the current implementation:
- handling of error pages registering with 4xx or 5xx
- for exceptions the exception hierarchy should be searched for a matching
error page
felix-4548-exception-hierarchy.patch tries to fix the second part. There is one
problem I ran into: in order to search the exception hierarchy I use
Class.forName to get the exception class. But this works only for exceptions
that are on the class path for the bundle containing the whiteboard
implementation (?). For a custom exception I created initially in the
integration test I got a ClassNotFound exception.
> Implement the missing errors registration
> -----------------------------------------
>
> Key: FELIX-4548
> URL: https://issues.apache.org/jira/browse/FELIX-4548
> Project: Felix
> Issue Type: Sub-task
> Components: HTTP Service
> Affects Versions: http-2.4.0
> Reporter: Simone Tripodi
> Assignee: Carsten Ziegeler
> Fix For: http.base-3.0.0
>
> Attachments: FELIX-4548.patch, felix-4548-exception-hierarchy.patch
>
>
> Current implementation of RFC189 does not support yet errors registration.
> Questions are:
> * do we want to have a servlet (or maybe a filter fits better)
> implementation which serves a static file whenever an HTTP error is detected?
> or
> * looking for a solution that delegates the underlying servlet container?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
