Cut,Copy,Paste do not appear to work in the error window
in the Processing IDE, so I'll hand-enter the error
for one of them:

"perhaps you wanted the overloaded version 'void
    glMultiMatrix(java.nio.FloatBuffer $1)' instead?"

Adding a zero worked (good news) but I don't know why.
The opengl red book specifies the argument that should
go to glMultiMatrix() as a 16 value float array. I do
not see an option for an offset as an argument. Is my
red book out of date (the pub date is 2004)?

....>>>>

Update on this message: In wading through the
javadoc for opengl, I found this:

glMultMatrixf(float[] m, int m_offset)
         Interface to C language function:

on this page:

http://download.java.net/media/jogl/builds/nightly/javadoc_public/

Welcome to incompatibility-land....

it's because the red book api is for c, and you're writing java code. the issue that's being addressed with the "offset" variable is that there's no way to provide an index into an array automatically, the way you can with c. for instance:

glMultMatrix(&blah[4]);
in c/c++ would allow you to pass the pointer to the 4th element in the array 'blah'. there's no way to reference a pointer in this manner using java, because it has no pointer math, therefore all you can do is:
glMultMatrix(blah, 4);
to do the same thing via the jogl api.

on the other hand, the floatbuffer stuff is another way of handling memory that's more efficient than passing arrays back and forth via JNI (passing data in JNI is very slow).

but if you don't like it, take it up with the JOGL developers at Sun. though they might just laugh, you'll find that the OpenGL interface to python, ruby, etc. will all differ from the c implementation as well.

Uploaded a version which works with 115.
http://v3ga.net/processing/ODEjava/Boxes_115.zip

"All GL calls where you pass in an array you need to add an extra offset parameter - 0 when refactoring" did the trick.

Hi ddf,
I just ported an example I coded with c++ (derived from one example found with ode package), using gl commands for drawing.
I was not aware of the AxisAngle4f representation, thanks for the tip.