[
https://issues.apache.org/jira/browse/AVRO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986570#action_12986570
]
Doug Cutting commented on AVRO-732:
-----------------------------------
For specific and reflect code, the natural mapping to me is that errors
declared in the protocol should be declared as thrown in the generated
interface methods. Generic code needs to throw something that's both an
exception and contains GenericRecord. Currently this is done by wrapping a
GenericData.Record within a AvroRemoteException.
I am still +1 for removing AvroRemoteException from the list of exceptions
thrown by generated code. Perhaps other exception-related improvements could
be made, but I'd prefer to limit this issue to that improvement if possible.
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
