[
https://issues.apache.org/jira/browse/AVRO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13530461#comment-13530461
]
Doug Cutting commented on AVRO-732:
-----------------------------------
Using a RuntimeException for undeclared errors is an improvement. But we
should perhaps also split the uses of AvroRemoteException into more than one
class. Its uses include:
- undeclared errors
- a base class for declared errors
- a wrapper for error data in the generic API
We might keep AvroRemoteException for the second use, add a new
RuntimeException named AvroUndeclaredException, a new GenericException
extending AvroRemoteException that's used by the Generic API. Is that
overkill? Can you think of a different re-factoring might break less user code?
> 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
>
>
> 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
