[
https://issues.apache.org/jira/browse/AVRO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13536572#comment-13536572
]
Doug Cutting commented on AVRO-732:
-----------------------------------
> you don't want to have a transport exception when implementing your interface
You don't have to throw or even declare every exception in an interface that
you implement. Still, having it in the interface may be confusing. Generating
two interfaces, one for remote clients and one for implementors, like Spring,
would be cleaner. Or we might just improve the documentation around this.
> AvroRemoteException in methods is viral [ on clients ]
This is like IOException. A checked exception for transport errors seems
appropriate on the client.
> 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
