How to Deploy a Stateless Session Bean

Instructions on how to deploy a stateless session bean

Remember to leave no spaces in the paths.

Install jboss 3.2.3
Install xdoclet 1.2.3 (from http://xdoclet.sourceforge.net)
Install lomboz (either into an existing eclipse or install the version that comes with an eclipse)
You need to have a JDK 1.4.2 installed too.
If you don't have it already, add the 1.4.2 JRE to the JRE definitions of eclipse.
In Window->Preferences, find xdoclet, it should be within J2EE annotations, and set the version to 1.2.3, and browse to where you installed xdoclet.
Expand Xdoclet and select ejbdoclet. Check JBoss and select version 2.3.
In Window->Preferences, select server, installed runtimes.
Add a new runtime with:

Type Generic JBoss 3.2.3(Generic)
Your JBoss home
Your JBoss home

Change to J2EE perspective and go to the Servers tab and add a server with the runtime that was specified in 9.
It should start and stop without problems.
Right-click on EJB Projects and select New- EJB Project
Specify:

Name SuDuelKuTestEJB
EJB version: 2.0
Target server: Generic JBoss 3.2.3(Generic)
Check Add module to EAR and Create EJB client JAR (although we won't use the EAR, the JAR is very useful)

Click finish

We will now create a new EJB.

Right-click on the EJB project and add New -> Enterprise Java Bean
Select Session Bean
Select:

Project: SuDuelKuTestEJB
Module name: same
Folder: keep the default
Package: you choose
Class Name: any name, but add Bean at the end of the name

Click next

Here we would choose the attributes of the bean. For now, everything stays the same.

Click finish
All the interfaces and the bean class are generated. The beauty of Lomboz is that you only need to change the NameBean class and everything gets updated with the xdoclet tags.
Open your class definition NameBean.java
Change the signature of method foo to receive something and return something interesting so we can check it later. When you save, an ant file should be run automatically.

Deploy the ejb:

This is the tricky part, hopefully there are no problems.
Open the folder with enterprise applications
Delete the EAR application that was created. Go ahead and delete the contents too.
Go to the servers tag and right-click on the server, and select Add and Remove Projects.
Select your bean and add it to the configured projects. (if we hadn't deleted the EAR, we wouldn't be able to do this, we would have to add all of the EAR to the server, and the EAR has a couple of empty deployment descriptors for the web part of the application).
Select finish.
Start the server and hope for no exceptions!

Some problems I encountered and their solutions:

If you get the message: enterprise-beans tag expected, it means that you are deploying the whole EAR application. We only want to deploy the EJB jar.
If you get the message: EJB spec violation, the methods in the remote interface must have a matching method in the bean's class. If your classes are correct, then it might be that the jars that are copied to the deploy directory of jboss are not being updated. Remove the project from the server, stop the server, select Project -> Clean, and clean both the EJB and the Client projects. Then redeploy the app. The problem should be gone.

Create the client:

The client project is already created, from when we created the EJB project.
Add JBoss client jar to the classpath.

Right-click the project, select properties. In Java Build Path, select add external Jars.
Find and add jbossall-client.jar on your JBOSS_HOME\client.

Add a new class.
Edit the class to include something similar to the code in the following table.

Note that YouWin was the name of my bean, and is the remote interface class. YouWinHome is the home interface that will give us the instance of the bean we will use (with create).
getContext() is a method that will give us our initial context (JNDI) to search for our bean. Those urls, classes and prefixes are specific to JBoss. The JNDI port and address is the default.
getHome returns an instance of our home interface.

Finally, call your EJB with some parameters, run the client as a standalone java application and hope for the best!

package ssd.mse.client;

import java.rmi.RemoteException;

import java.util.Hashtable;

import javax.ejb.CreateException;

import javax.naming.InitialContext;

import javax.naming.NamingException;

import ssd.mse.YouWin;

import ssd.mse.YouWinHome;

public class YouWinClient {

/**

* @param args

private YouWinHome getHome() throws NamingException

{

return (YouWinHome) getContext().lookup(YouWinHome.JNDI_NAME);

}

private InitialContext getContext() throws NamingException

{

Hashtable props = new Hashtable();

props.put(InitialContext.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");

props.put(InitialContext.PROVIDER_URL, "jnp://localhost:1099");

props.put(InitialContext.URL_PKG_PREFIXES, "org.jboss.naming:org.jnp.interfaces");

//java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory

//java.naming.provider.url=jnp://localhost:1099

//java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces

InitialContext initialContext = new InitialContext(props);

// InitialContext initialContext = new InitialContext();

return initialContext;

}

public void testBean()

{

try

{

YouWin myBean = getHome().create();

System.out.println("Result: " + myBean.youWin("Lucia"));

}

catch (RemoteException e)

{

e.printStackTrace();

}

catch (CreateException e)

{

e.printStackTrace();

}

catch (NamingException e)

{

e.printStackTrace();

}

public static void main(String[] args)

{

YouWinClient test = new YouWinClient();

test.testBean();

}