Exception being thrown using jogl v2.2.0

Hello,
My company has some webstart applications which use the jogl extension at the bottom of this message to access native jogl libs.  Since the switchover to v2.2.0, all of our apps have been throwing the following exception:

Exception in thread "AWT-EventQueue-2" javax.media.opengl.GLException: Caught NoSuchMethodError: com.jogamp.opengl.FBObject.createColorTextureAttachment(Ljavax/media/opengl/GLProfile;ZII)Lcom/jogamp/opengl/FBObject$TextureAttachment; on thread AWT-EventQueue-2
        at javax.media.opengl.GLException.newGLException(GLException.java:75)
        at jogamp.opengl.GLDrawableHelper.invokeGLImpl(GLDrawableHelper.java:1318)
        at jogamp.opengl.GLDrawableHelper.invokeGL(GLDrawableHelper.java:1138)
        at javax.media.opengl.awt.GLCanvas$11.run(GLCanvas.java:1368)
        at javax.media.opengl.Threading.invoke(Threading.java:223)
        at javax.media.opengl.awt.GLCanvas.display(GLCanvas.java:522)
        at javax.media.opengl.awt.GLCanvas.paint(GLCanvas.java:576)
        <more>

If I revert back to using v2.1.5, things run just fine.  Any ideas what's wrong would be appreciated.  Is this a bug in 2.2.0 or is there something we need to change in our apps?

The extension url being used in the jnlp:
http://jogamp.org/deployment/jogamp-current/jogl-all-awt.jnlp

Thank you,
Dave Peterschmidt

On 08/07/2014 07:17 PM, dpetersc [via jogamp] wrote: Yes, 2.2.0 is not bwd compatible w/ 2.1.5, see wiki version semantics
and maybe even our 'semver' unit test results.

You need to recompile and adapt.

~Sven

dpetersc, it has been modified to fix the bug 1009:
https://github.com/sgothel/jogl/commit/d354cf767182c27f44ad4c00d2e975f8d689daa8#diff-fce9a8281cd4cdd358b650b8edb39189

You just have to pass a GL instance instead of a GLProfile instance.

Ok, thanks for the responses.  Much appreciated.

Just a general observation here, it might not be a good idea to make releases that are not backward compatible when you have a "current" pointer that flips automatically.  You're going to break the software of anyone who uses that pointer and hasn't prepped for your release.


 

You're welcome.

Actually, JOGL 2.2.0 is the current version. If you wanted to go on using JOGL 2.1.5, you could use this URL:
http://jogamp.org/deployment/v2.1.5/

If the developers don't want their softwares to be broken, they should point out to the most appropriate version. You can use the current version when you're sure you're compatible with it. When your software isn't ready to support the latest release, it shouldn't point out to jogamp-current or jogamp-next. Is there anything unclear?

Yep, we've come to the same conclusion and have a change in the works now to move to the direct 2.1.5 url.    

Again, thanks for your help, and thanks for maintaining this resource.  It really helps with our webstart effort.

I admit that it would have been better to drive the method deprecated before removing it but there is no version 2.1.6, it explains why we were allowed to modify the public API (2.1 -> 2.2).