Copy the EntWizard_JBoss3x_JB9_v3.1.jar file to the Jbuilder9 lib/ext directory. I have re-written this tool for JB9 using the latest
opentools API. Most of the classes have been deprecated since JB8/JB7 so this version for JB9 is totally up to date.
Copy JBossDTD.jar to the JBuilder9 lib/ext directory. This opentool will allow you to select your dtd's based on the version of
JBoss you are running. After it is installed, Go to the Tools menu and select JBossDTD. Choose your DTD version, select OK and
this will save your configuration. Then you can setup the server as explained below.
I included the DTD version 4 in the setup, however I am still working on EntWizard for JBoss 4x so I can't say if everything is working.
Start JBuilder.
Under Tools/Configure Servers, select JBossApplicationServer3x and select the Enable Server checkbox.
Select the Home Directory of the JBossApplicationServer3x distribution. For example C:\jboss-3.2.0_tomcat-4.1.24
Next select the Custom tab and after accepting the license agreement select the directory where the jasper-compiler.jar and jasper-runtime.jar files are located on your system.
While still on the Custom tab click OK.
Restart JBuilder.
If on restarting JBuilder, JBoss is not selected as your appserver, go to Project Properties and select the Server tab. Choose JBossApplicationServer3x and click ok.
Under required libraries tab, select "JBossApplicationServer3x servlet", and "Ant" to add to the required libraries path. You then have to create a new library containing the j2ee.jar file from you java JDK you have installed.
NOTES
1) local-jndi-name tag is now created in the jboss.xml file. To input a value for the local-jndi-name, select the ejb node, and under the General Tab input the value for "Local Home JNDI Name".
2) Message Driven Beans values are input under the message-driven-beans tab when the MDB node is selected. To input the value for destination-jndi-name, go to the JBossApplicationServer3x Properties tab.