From: Laurent Bobelin Date: Thu, 10 Nov 2011 14:18:55 +0000 (+0100) Subject: Added an index page for javadoc X-Git-Tag: v3_9_90~569^2~19^2~166 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/ecf45d6adfeb07db1db20531e0775467a706dcc8 Added an index page for javadoc --- diff --git a/doc/Doxyfile.in b/doc/Doxyfile.in index 924384f527..f8df3fa644 100644 --- a/doc/Doxyfile.in +++ b/doc/Doxyfile.in @@ -613,7 +613,8 @@ WARN_LOGFILE = # directories like "/usr/src/myproject". Separate the files or directories # with spaces. -INPUT = @srcdir@/doc/install.doc \ +INPUT = @srcdir@/doc/index.doc \ + @srcdir@/doc/install.doc \ @srcdir@/src/ # This tag can be used to specify the character encoding of the source files diff --git a/doc/index.doc b/doc/index.doc new file mode 100644 index 0000000000..b0ee82b7aa --- /dev/null +++ b/doc/index.doc @@ -0,0 +1,23 @@ +/*! \page index Java Binding documentation home page + +\section welcome Welcome to Simgrid-java documentation home page + + +Simgrid-java is a java API that let you use SimGrid MSG API in your favorite language (java). Without it, you would be forced to use C or one of the other bindings provided. + +To make a long story short, it's a JNI binding, so it implies that : +\li Most of the MSG and SimGrid documentation about behavioral aspects applies directly to what you are programming. +\li MSG data structures are mapped to Java objects. So it means that from the syntaxic point of view, you have to know how those objects are. Fortunately, we have generated the Javadoc for those objects. So take a look at it + +Finally, it implies also that you program can crash for 3 main reasons : + +\li Your Java part is not good : you'll have a good old java exception thrown, and hence you should be able to correct it by yourself. +\li Our java part is not good : you'll also have a java exception thrown, but we have real doubts this can happen, since the java part is only a JNI binding. The other option is that it crashed because you used incorrectly the MSG API, so this means also you should have a MSGException. It means you should read carefully MSG samples and/or documentation. +\li Something has crashed in the C part. Okay, here comes the tricky thing. + +C crashes mainly for 2 reasons : + +\li When something goes wrong in your simulation, sometimes the C part stops because you used SimGrid incorrectly, and JNI bindings are not fond of that. It means that you'll have something that looks ugly, but you should be able to identify what's going wrong in your code by carefully reading the whole error message +\li It may happen that the problem comes directly from SimGrid : in this case, the error should be uglier. In that case, you may submit a bug directly to SimGrid. + + */