[
https://issues.apache.org/jira/browse/AVRO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534159#comment-13534159
]
Doug Cutting commented on AVRO-732:
-----------------------------------
I'm now starting to worry that switching to an unchecked exception might make
it more difficult to write distributed applications. Remote procedure calls
are more likely to fail in than local procedure calls and those failures are
often recoverable. Distributed applications often explicitly consider the
failure of every remote call. Every RPC involves i/o, so always throwing some
IOException might be reasonable.
Does that make any sense? What is the bug we're trying to fix here?
> Generated protocol's method should not throw AvroRemoteException
> ----------------------------------------------------------------
>
> Key: AVRO-732
> URL: https://issues.apache.org/jira/browse/AVRO-732
> Project: Avro
> Issue Type: Bug
> Components: java
> Reporter: Sharad Agarwal
> Fix For: 1.8.0
>
> Attachments:
> AVRO-732-remove-generated-remote-exception-2012-12-11.patch,
> AVRO-732-remove-generated-remote-exception-2012-12-17.patch
>
>
> If user does NOT define the throws clause in the idl, the code is generated
> with "throws AvroRemoteException" clause. However on throwing the
> AvroRemoteException from the implementation, the serialization fails. This is
> not intuitive to users.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
