JBoss.orgCommunity Documentation

Mobicents JAIN SLEE SleeConnectivity Example User Guide


This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information.

In PDF and paper editions, this manual uses typefaces drawn from the Liberation Fonts set. The Liberation Fonts set is also used in HTML editions if the set is installed on your system. If not, alternative but equivalent typefaces are displayed. Note: Red Hat Enterprise Linux 5 and later includes the Liberation Fonts set by default.

Four typographic conventions are used to call attention to specific words and phrases. These conventions, and the circumstances they apply to, are as follows.

Mono-spaced Bold

Used to highlight system input, including shell commands, file names and paths. Also used to highlight key caps and key-combinations. For example:

The above includes a file name, a shell command and a key cap, all presented in Mono-spaced Bold and all distinguishable thanks to context.

Key-combinations can be distinguished from key caps by the hyphen connecting each part of a key-combination. For example:

The first sentence highlights the particular key cap to press. The second highlights two sets of three key caps, each set pressed simultaneously.

If source code is discussed, class names, methods, functions, variable names and returned values mentioned within a paragraph will be presented as above, in Mono-spaced Bold. For example:

Proportional Bold

This denotes words or phrases encountered on a system, including application names; dialogue box text; labelled buttons; check-box and radio button labels; menu titles and sub-menu titles. For example:

The above text includes application names; system-wide menu names and items; application-specific menu names; and buttons and text found within a GUI interface, all presented in Proportional Bold and all distinguishable by context.

Note the > shorthand used to indicate traversal through a menu and its sub-menus. This is to avoid the difficult-to-follow 'Select Mouse from the Preferences sub-menu in the System menu of the main menu bar' approach.

Mono-spaced Bold Italic or Proportional Bold Italic

Whether Mono-spaced Bold or Proportional Bold, the addition of Italics indicates replaceable or variable text. Italics denotes text you do not input literally or displayed text that changes depending on circumstance. For example:

Note the words in bold italics above username, domain.name, file-system, package, version and release. Each word is a placeholder, either for text you enter when issuing a command or for text displayed by the system.

Aside from standard usage for presenting the title of a work, italics denotes the first use of a new and important term. For example:

If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in the the Issue Tracker, against the product Mobicents JAIN SLEE SleeConnectivity Example, or contact the authors.

When submitting a bug report, be sure to mention the manual's identifier: JAIN_SLEE_SleeConnectivity_EXAMPLE_User_Guide

If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily.

  1. Downloading the source code

    Use SVN to checkout a specific release source, the base URL is http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/examples/slee-connectivity, then add the specific release version, lets consider 2.4.0.CR1.

    [usr]$ svn co http://mobicents.googlecode.com/svn/tags/servers/jain-slee/2.x.y/examples/slee-connectivity/2.4.0.CR1 slee-example-slee-connectivity-2.4.0.CR1
  2. Building the source code

    Important

    Maven 2.0.9 (or higher) is used to build the release. Instructions for using Maven2, including install, can be found at http://maven.apache.org

    Use Ant to build the binary.

    				    [usr]$ cd slee-example-slee-connectivity-2.4.0.CR1
    				    [usr]$ mvn install
    				    

    Once the process finishes you should have the JAIN SLEE deployable-unit jar file in the slee/du/target directory, and JMX Client in the javaee/beans/target directory.

Similar process as for Section 2.2.1, “Release Source Code Building”, the only change is the SVN source code URL, which is http://mobicents.googlecode.com/svn/trunk/servers/jain-slee/examples/slee-connectivity.

Important

To obtain the example's complete source code please refer to Section 2.2, “Mobicents JAIN SLEE SleeConnectivity Example Source Code”.

JMX Client is defined by two elements: XML descriptor and POJO class.

XML descriptor is very simple. It looks as follows(jboss-beans.xml):



<?xml version="1.0" encoding="UTF-8"?>

<deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns="urn:jboss:bean-deployer:2.0">

    <bean name="SleeConnectionTest"
        class="org.mobicents.example.slee.connection.SleeConnectionTest">
        <annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(
            name="org.mobicents.slee:name=SleeConnectivityExample",exposedInterface=
            org.mobicents.example.slee.connection.SleeConnectionTestMBean.class
                ,registerDirectly=true)
        </annotation>       
    </bean>

</deployment>
        
            

Descriptor has following elements present:

Client contract is defined by implemented interface class, that is org.mobicents.example.slee.connection.SleeConnectionTestMBean

Concrete implementation can be found in org.mobicents.example.slee.connection.SleeConnectionTest class.



            
        public void fireEvent(String messagePassed) {
        // depending on deployment it does following:
        // 1. lookup RA and make RMI calls through it
        // 2. lookup local Bean, which makes direct calls to container!
        logger.info("Attempting call to SleeConnectionFactory.");
        try {
            InitialContext ic = new InitialContext();
            // this is call to local JNDI space, private, it cant be accessed
            // from other JVM
            SleeConnectionFactory factory = (SleeConnectionFactory) ic
                    .lookup("java:/MobicentsConnectionFactory");
            SleeConnection conn1 = null;
            try {
                conn1 = factory.getConnection();
                ExternalActivityHandle handle = conn1.createActivityHandle();
                EventTypeID requestType = conn1.getEventTypeID(eventName,
                        eventVendor, eventVersion);
                CustomEvent customEvent = new CustomEvent();
                customEvent.setMessage(messagePassed);
                logger.info("The event type is: " + requestType);
                conn1.fireEvent(customEvent, requestType, handle, null);
            } finally {
                if (conn1 != null)
                    conn1.close();
            }
        } catch (Exception e) {
            logger.error("Exception caught in event fire method!", e);
        }
    }
            

Revision History
Revision 1.0Tue Dec 30 2009Eduardo Martins
Creation of the Mobicents JAIN SLEE SleeConnectivity Example User Guide.