Monday, November 22, 2010

Roadmap for Mobicents JAIN SLEE 3.0

You can now see the draft roadmap for Mobicents JAIN SLEE 3.0 at In summary we are going to implement the more radical JAIN SLEE 1.1 extensions, Java annotations (community discussion to start soon) and the advanced ConfigProperties idea, which should result in a very different programming model. But changes/enhancements will touch the whole platform:

  • Cluster Enhancements: More flexible framework (with respect to what is used as datasource to hold clustered state), a more useful and feature rich buddy groups setup
  • Resource Adaptors: JSR 309 finally, a easy to customize "example" JDBC/Datasource RA, same for a Web Services Client RA, and an alternative Http Server RA that does not relies on HTTP Servlets
  • Service Enablers: continue the work started by the XDM Client, providing ready to integrate enablers for SLEE applications
  • Web Console 3.x: still a bit undefined at this point, but very high chances that we will have the "old" web console back, and leave Jopr/JBoss ON just for monitoring

We have set the first Beta version for the end of January, and set all the new stuff for such release, but note that it is expected some to miss the train and jump in later releases, the task list is so big. Still, our compromise is that in the middle of the year we will have the first FINAL release, and such release will have everything production quality and carrier grade.

Finally, if you have been wanting to contribute but not able to understand how, this time is a great opportunity to step in, it's specially easy to contribute on components such as the new resource adaptors and enablers.

All feedback is welcome so please let us know what's in your mind.


  1. Anonymous4:05 PM

    Why the need for a management console ? IIRC, there was a discussion in the community long back where we decided that JON will act as a console.

    Regarding JDBC RA, will it maintain the connection pool at the RA level, or will it re-use the underlying JBOSS connection pooling ? Let me know if you need any help regarding these new developments.

    I also have some inputs on the web-services RA and some interesting use cases for which it can be applied.


  2. The problem is that JON is not good for anything else than monitoring, it includes too many UI limitations, and it is very sluggish. It is also expected that JBoss AS7 comes with a new web admin tool.

    Regarding JDBC my idea would be for each entity to connect to a specific datasource in JBoss AS, thus re-using all pooling.

    Wrt Web Services, please post that feedback in mobicents-public ;)