On Thu, 16 Mar 2000, Kevin A. Burton wrote:
> Jeff Prickett wrote:
> >
>
> +1. We also need a JetspeedException which PortletException and
> ICalendarException would extend. This an app could just catch
> JetspeedException to become more generic.
>
Cool, I have been working on this problem this morning a bit. As soon as I
get a clean build. I will check it in. I will certainly add the
JetspeedException in there as the parent class. I will put
the Jetspeed Exception in package org.apache.jetspeed.util.
Also, I tried to get functionality from recasting the exception.
Specifically, if either a key or its corresponding message are not found
it tells the user to contact the Jetspeed list. The error messages for the
MessageResources were generic to apply to all cases, but since we were
going to rethrow the exception I was able to give some more context
specific information.
> ...
>
> We should also have a way to combine multiple project resources. I mean
> so that we can have TurbineResources and JetspeedResources all via a
> TurbineResource Service/Avalon block. This would have to be namespaced
> though and would require some property rewrites. Then these would just
> throw a ResourceException instead of just Exception.
>
> --
<snip>
I am going to have to hold off on this for now, mostly because it seems
like this would require some further discussion/research. Maybe a TODO
list item.
Jeff Prickett
[EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]