Add this to your .proto file:

  option java_multiple_files = true;

Note that the outer class is still generated, it just doesn't contain the
other classes.  You can still change the outer class name with:

  option java_outer_classname = "Whatever";

On Mon, Nov 9, 2009 at 6:47 PM, sansun08 <>wrote:

> To be more precise, how do I avoid the inner class implementations in
> the auto-generated code by protobuf(java). I want the java file name
> to be same as the Message name which also implies that the message
> class should not be an inner class. Is there a way to achieve this(In
> short similar to DAO classes used by ejb or hibernate)?
> On Nov 10, 6:32 am, sansun08 <> wrote:
> > I am not asking specific to torque. Were there any successful attempt
> > in integrating with any of the famous ORMs like hibernate or JPA?
> >
> > On Nov 9, 11:03 am, sansun08 <> wrote:
> >
> > > We use <a href="";>apache
> torque</
> > > a> as ORM in our project. The DAOs( torque auto generates the DAO
> > > classes based on the schema design) generated are quite complex( since
> > > our database schema design is really complex). We use readExternal and
> > > writeExternal to deserialize /serialize objects. We already face some
> > > serious performance issues when the data is large. I think protobuf
> > > can definitely make things better for our case. Is there a way to
> > > integrate Protobuf classes with our existing DAO model?
> >

You received this message because you are subscribed to the Google Groups 
"Protocol Buffers" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to