The Java bindings were revised because (a) the old ones had significantly bit-rotted, (b) we wanted to improve performance by making the code truly a "binding" instead of just a wrapper around MPI calls, and (c) we wanted to extend coverage to all of the current MPI standard. Hence the changes.
The bindings are now stable, which is why they are now coming to a release series. Things in our devel trunk are not guaranteed stable. Note that things in a "feature" series (one that has an odd number in the second part - e.g., 1.7) are not necessarily fully stable as they can undergo changes prior to inclusion in a "super-stable" series (an even number in the second part). At that time, only bug fixes are allowed. That said, we don't anticipate changes to the Java binding APIs. The new bindings are documented via javadocs and man pages, which should help in the transition. If you have specific questions, I suspect some of the folks more directly involved will try to help. HTH Ralph On Tue, Dec 3, 2013 at 2:22 AM, Ivan Borisov <68van...@mail.ru> wrote: > Hello everyone. > > I've installed nightly 1.7.4 recently and it's Java API is completely > different from mpiJava. > Is there guide or something to new Open MPI Java bindings? Or will it > come out later (in some resonable time)? > Specifically, I'm interested in how to port existing sources from old > mpiJava to new Open MPI Java bindings > and comments explaining reasons of changing each part of API. > Is there determined time when new Java bindings will become stable or > it's done when it's done? > Also, what is the best version of Java API implementation for now? > > Sorry if I'm asking too much :) > > Thanks, > Ivan Borisov. > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users >
