[
https://issues.apache.org/jira/browse/AVRO-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12985032#action_12985032
]
Scott Carey commented on AVRO-732:
----------------------------------
The code always adds AvroRemoteException if is not a one-way message:
in the compiler's velocity template protocol.vm there is:
{quote}
)#if (! $message.isOneWay())
throws org.apache.avro.AvroRemoteException##
{quote}
and corresponding logic in the Avro14SpecificCompiler test class.
Is it OK to remove this? Or is the suggestion that if an exception is
declared, then omit the AvroRemoteException? If we get rid of it completely,
what is the expected behavior when the remote side sends back an error? I'm
not familiar enough with the protocols to fix this, but we should do so for
1.5.0 since the exception signature is changing due to AVRO-737.
> 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.
