Justin Santa Barbara wrote:
@SuppressWarnings("all")
public interface BulkData {
ByteBuffer read() throws AvroRemoteException;
Void write(@Named("data") ByteBuffer data) throws AvroRemoteException;
}
I've taken a different approach in AVRO-185.
https://issues.apache.org/jira/browse/AVRO-185
There I simply added the protocol to the generated interface, so
reflection need no longer be used to determine the method list, nor
method parameter names.
I'm guessing there's some historical reason here - can anyone fill me in on
the reasoning?
The historic reason is that reflect was implemented before specific, and
specific was built to depend on reflect. Reflect already had a means to
get the method list (including parameter names) from an interface, so
none was added for specific.
Doug
