I wish we could have just one style, but I think it's pretty clear that different people are going to keep wanting a variety of options on or off. Usually you are separated from other coders' code generator decisions by the transport, but I don't really know of a way around that with an embedded server.
On Fri, Aug 27, 2010 at 1:17 AM, Mathias Herberts < [email protected]> wrote: > Thanks for contributing this. > > On the minus side, I don't like the idea of having several types of > Java code generated from one IDL as this might lead to some problems > later. > > One example I ran into is when running an embedded Cassandra in some > tests. All Java code I generate from Thrift IDLs uses bean syntax, > this is not the path that was choosen by the Cassandra folks, > therefore to access the embedded Cassandra using the generated Client > code (bean style), you need to remove all other generated classes > otherwise the embedded Cassandra won't work. > > So my wish would be for one and only one type of Java code being generated. > > > Mathias. >
