Agorava Core 0.6.1 released

Posted by Antoine Sabot-Durand on Aug 07, 2013 | Comments

Agorava core version 0.6.1 just hit Maven Central today, it corrected some issues in 0.6.0 and added interesting features.

Release notes


  • [AGOVA-33] – NPE when no OAuthSession producer is found
  • [AGOVA-34] – Unserializable exception for OAuthSession on Wildfly 8.0


  • [AGOVA-35] – Add Weld 2.0 Test profiles
  • [AGOVA-39] – Adopt JBoss Community code formating
  • [AGOVA-45] – Switch to a BOM model
  • [AGOVA-46] – Officially switch to git flow maven plugin for release

Feature Request

  • [AGOVA-36] – No more resetConnection() in 0.6.0
  • [AGOVA-37] – Add a Servlet to manage callback in OAuth Dance

What does it mean in plain english? Let’s see.

CDI 1.1 and Weld 2.x support

A big thanks to Aslak Knustsen on this point. He added profiles to launch test with Weld 2.x and correxted some issue with Agorava CDI extension preventing it to run under CDI 1.1.
Agorava now support OpenWebBeans 1.1.7 and Weld from 1.1.5 to 2.0.2. We’ll continue to extends CDI support in next release especially with OpenWebBeans 2.x when it’ll be ready.

Servlet to manage callback in OAuth initialization

An old feature request was achieved in this release the callback servlet that deal with the end of OAuth initialization process. Its default behavior is to close the current window (working for a popup) but you can easily override it to add your behavior.

Dependency Management with maven BOM

Dependencies are now managed by a Maven Bill Of Material, it will allow Agorava users to integrate Agorava dependencies more easily than with a parent pom. You’ll just have to add this to the `dependencyManagement` section of your project :



Again, many thanks to Aslak Knutsen for his help and to George Gastaldi for his feedback and work on PicketLink integration.

What’s next ?

Version 0.7.0 has started (for real this time), we’re going to integrate our own OAuth engine to prepare migration to OAuth client framework and add support to Apache Camel to provide better integration solution (especially for Social Media providing Streaming API).
In the meantime go for :


check our Getting Started guide and give us your feedback