It seems I often call api code not under the javaapi package as well (primarily in our container code which embeds a KafkaServer instance), but also in some client code. Thus, it seems the javaapi is not meant to be a single-point of entry, no?
Jason On Thu, Nov 29, 2012 at 4:31 PM, Jay Kreps <[email protected]> wrote: > I think what Subhash is asking for is just plain old fashioned javadoc. > People are used to having that for java apis. We should do that, but I > think it would require moving the java-friendly wrappers into java. This > would probably be a good thing to do anyway just to get rid of all the > crazy scala methods. > > -Jay > > > On Thu, Nov 29, 2012 at 3:31 PM, Joel Koshy <[email protected]> wrote: > > > Are you referring to the scaladoc? > > http://people.apache.org/~joestein/kafka-0.7.1-incubating-docs/ There's > > (some) documentation on the java api as well (i.e., the javaapi packages) > > that you can use from Java. > > > > Joel > > > > > > On Thu, Nov 29, 2012 at 3:14 PM, Subhash Agrawal <[email protected] > > >wrote: > > > > > Hi All, > > > > > > I am new to Kafka and we are planning to use Kafka as message broker. > > > > > > I am wondering if there are java API documentation for Kafka. I noticed > > > that current API doc is written for Scala user. I believe it could be > > > because it is written > > > in Scala. > > > > > > Please let me know. > > > > > > Thanks > > > Subhash A. > > > > > >
