need a way to pass the exceptions generated in filters to the Grizzly user

[glassfishrobot]

I'm filing this issue to track the earlier discussion around exception handling
around read or any other similar filters in Grizzly. Here is detail description
of the problem, in the email archive :

https://grizzly.dev.java.net/servlets/ReadMsg?list=dev&msgNo=680

The scenario is, when an exception happens (say, a connection error, or a parser
error while parsing..) the developer of Grizzly would like to take some
definitive action in the application. This requirement applies to both server
and client side.

Its a good idea to have a callback mechanism (or event handling /listeners) to
register for a specific exceptions and then pass them to the registered objects
for action upon their occurrence.

Environment

Operating System: All
Platform: Sun

Affected Versions

[1.9.22]

[glassfishrobot]

Reported by raih@java.net

[glassfishrobot]

Was assigned to oleksiys@java.net

[glassfishrobot]

jfarcand@java.net said:
I agree this is important I'm turning it into a bug and a p2 so we can a fix
sooner that later

Thanks!

[glassfishrobot]

oleksiys@java.net said:
Fixed

Author: oleksiys
Date: 2008-01-11 19:51:42+0000
New Revision: 697

Modified:
trunk/modules/grizzly/src/main/java/com/sun/grizzly/DefaultProtocolChain.java

Log:
Fix for issue#43

[glassfishrobot]

jfarcand@java.net said:
Fix target

[glassfishrobot]

Marked as fixed on Wednesday, December 16th 2009, 6:14:11 pm

[glassfishrobot]

This issue was imported from java.net JIRA GRIZZLY-43