[
https://issues.apache.org/jira/browse/DIRMINA-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531268
]
Trustin Lee commented on DIRMINA-249:
-------------------------------------
One problem with introducing WriteException is that any existing IoFilters that
filter a WriteRequest also need to filter WriteException to provide the
original message object user specified in IoSession.write() call, like they do
for messageReceived and messageSent events. Therefore, the implementation of
IoFilter becomes more complex.
> exceptionCaught() should provide more information
> -------------------------------------------------
>
> Key: DIRMINA-249
> URL: https://issues.apache.org/jira/browse/DIRMINA-249
> Project: MINA
> Issue Type: Improvement
> Environment: All
> Reporter: Vinod Panicker
> Fix For: 2.0.0-M1
>
>
> Currently if the application calls a write() on MINA, it will get notified of
> any exceptions via the exceptionCaught() method. The problem is that the
> application does not have any information as to what data could not be
> written on the session. To figure that out, it either has to wait on the
> WriteFuture or implement some state mechanism within the IoSession.
> Trustin recommended that a WriteException could be created, which could
> provide the necessary information. It should have the ByteBuffer for which
> the write() failed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
