Friday, August 07, 2009

Mobicents JAIN SLEE 2.0.0.BETA1

The loooooooooong waited first BETA version of Mobicents JAIN SLEE 2.x is out!!!! JBoss AS 5, JAIN SLEE 1.1, better performance, it all there already. See the official release announcement.

Since the container now supports JAIN SLEE 1.1, the old scheme to include library jars in deployable units is not supported, instead you should create JAIN SLEE library jars, and too make it easier we developed a new Maven2 plugin, where, putting it simple, you just configure the library id, put classes/resources in usual places, define jars to be include as default scoped dependencies. You can even define references to other libraries using dependencies with runtime scope, and the plugin will grab the library id of the referenced library automatically. Needless to say, the plugin generates the library-jar.xml XML descriptor for you and makes the jar, cool uh? :) A complete wiki page about the plugin is on the works, but you can take a look at one example here.

The maven DU plugin was also updated to 2.0.0.BETA1, defining own packaging "jainslee-du", being faster on the build process, and generating JAIN SLEE 1.1 XML descriptors. The plugin now deploys DU jars into Maven repositories, which open new possibilities for a remote DU management, kind of a SLEE online component store. See an example using new version of this plugin.

On a side note, for this BETA version of the container, people used to deploy/undeploy deployable units through file copy, what we call hard deploy, need to include a jboss-classloading.xml file in the deployable unit META-INF such as this one. This is due to some incompatibilities in class loading of the underlying JBoss AS5 Microcontainer deployers.

See you soon for some posts about JAIN SLEE 1.1 new features.

PS: Next version, BETA2, will bring Fault Tolerance and new management console, scheduled to September of this year, hooraay ;)


  1. About the maven du plugin. Its good work. I use it to generate the du descriptor.

    However, I use jboss maven plugin to deploy into jboss deploy directory:

    mvn jboss:harddeploy

    And I use maven's built-in deploy plugin to upload into a repository:

    mvn deploy

    I attach the du plugin to the generate-resources phase, and use the 'jar' package, not jainslee-du package. I find this to be more similar to my experience of maven before I started using mobicents.

    I wonder what the roadmap is for mobicents maven plugin.

  2. Hi John, tks for the feedback, regarding your way to use the plugins:

    . maven jboss plugin - last time I tried it there was no hard undeploy, but seems it was now added, I will try :)

    . regarding maven deploy plugin, that is what we use also, directly for daily snapshots, or through maven release plugin when doing releases

    . jar vs jainslee-du packaging - it is ok to use it that way, it is coherent with maven model since the deployable-unit-jar.xml is a generated resource, yet by having our own packaging we can also easily identify deployable units, and may bring cool features in the future such a online jain slee deployable unit repository, acessible in a console on server runtime (same idea as app stores in mobiles), the plugin code really is nothing more than the jar plugin that generates the DU jar and ant script.

    Finally, regarding the roadmap, there is nothing really planned except let some time roll and see if it is stable enough to become a GA version. The plugin does what it is intended and we have not tought on new features, do you want to propose something? :)

  3. Hi Eduardo,

    I would like to know when will annotations programming model be available at Mobicents.

    This is a fantastic project. Congratulations for the excellent job.

  4. Probably *we* won't have time to start such work till the end of the year, the time scheduled for the first JAIN SLEE 2.0 GA release, but any community move before that is more than welcome and will be embraced :)