Hi£¬
Agree with it basically.
There is note about Exception:
GrizzlyException must not return null on getMessage() called.
If other Application getMessage(aGrizzlyException)==null ,
mostly there would be a NPE.
so getMessage(){
String msg = cause.getMessage();
if(msg==null)return cause.getClass().getSimpleName():
....
}
And about logger,
again, another big problem.
You think merge or include slf4j into grizzly would be what?
yes, sun logggggger, human knows, there are many words on all loggers.
One words, If grizzly do self more complex logger wrapper,
or use java.util.logging.Logger, I myself would not happy, really just like
thorn in my throat.
Regards,
2007/7/19, charlie hunt <charlie.hunt_at_sun.com>:
>
> One of the agenda items from today's Project Grizzly meeting was to pull
> out a document we had written internally as a proposal for exception
> handling and logging in Grizzly. Then, post this to Project Grizzly as
> a proposal and gather feedback from the document.
>
> A copy of this document can be found here:
>
> https://grizzly.dev.java.net/meetingMinutes/GrizzlyExceptionHandlingAndLogging.html
>
> Feel free to offer your feedback and comments.
>
> As mentioned in the meeting minutes, there is no time frame or release
> to which this proposal will be implemented. We are taking the first
> steps at floating the proposal. After reviewing comments, suggestions,
> etc we will hopefully identify someone who can do the implementation.
> When that occurs we will determine which release this proposal will
> become part of.
>
> So, please review the document and provide comments by responding to
> e-mail.
>
> thanks,
>
> charlie ...
>
> --
>
> Charlie Hunt
> Java Performance Engineer
> 630.285.7708 x47708 (Internal)
>
> <http://java.sun.com/docs/performance/>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>
>
--
ÏòÇØÏÍ