WTP 1.5: Serverdefinition for JBoss 4.0.4/4.0.5 with EJB3 support, for JBoss 4.2.0 and for JBoss 5.0.0
Plugin overview and installation
With some small modifications I was able to use WTP 1.5 to develop a JEE5 enterprise application.
To use the plugin:
* JBoss 4.0.x: You MUST have installed the EJB3 RC9 to the default configuration so that the plugin can find all required libraries.
For JBoss 4.0.4 with installer including EJB3 RC8 this is done automatically.
For EJB3 RC 9 there is no JBoss AS installer, it must be installed to the default configuration manually. Later you can install EJB3 RC9 to any other configuration, the jars from the default configuration are only needed for starting up application clients and for Eclipse.
* JBoss 4.2.0: the default configuration must be present so that the plugin can find all required libraries (tested for CR1 to GA)
* JBoss 5.0.0: the default configuration must be present so that the plugin can find all required libraries (tested for Beta2)
* Delete previous versions of this plugin if already installed.
* Download org.eclipse.jst.server.jboss.ejb3_1.5.0.v200706052200.jar
* Copy the file to the subdirectory "plugins" of your eclipse installation.
* Restart eclipse once with the "-clean" option: "eclipse -clean".
* Create a new server runtime. You will find the runtimes in the "JBoss" branch, labeled "JBoss 4.0.4 or 4.0.5 with EJB3 RC8 or RC9", "JBoss 4.2.0" or "JBoss 5.0"
The plugin does not more than adding some additional JAR files to the project build path:
JBoss 4.0.x:
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-ejb3x.jar
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
* JBOSS_HOME/server/default/lib/hibernate3.jar
* JBOSS_HOME/server/default/lib/hibernate-annotations.jar
JBoss 4.2.0:
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
* JBOSS_HOME/server/default/lib/jboss-ejb3x.jar
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
* JBOSS_HOME/server/default/lib/hibernate3.jar
* JBOSS_HOME/server/default/lib/hibernate-annotations.jar
* JBOSS_HOME/client/commons-logging.jar
* JBOSS_HOME/client/javassist.jar
* JBOSS_HOME/client/antlr.jar
* JBOSS_HOME/server/default/lib/servlet-api.jar (in 4.0.x: "javax.servlet.jar")
* JBOSS_HOME/server/default/lib/jsp-api.jar (in 4.0.x: "javax.servlet.jsp.jar")
JBoss 5.0.0:
* JBOSS_HOME/server/default/deployers/ejb3.deployer/jboss-ejb3.jar
* JBOSS_HOME/server/default/deployers/ejb3.deployer/jboss-ejb3x.jar
* JBOSS_HOME/server/default/deployers/ejb3.deployer/jboss-annotations-ejb3.jar
* JBOSS_HOME/lib/jboss-aop-jdk50.jar
* JBOSS_HOME/server/default/deployers/jboss-aop-jboss5.deployer/jboss-aspect-library-jdk50.jar
* JBOSS_HOME/server/default/lib/hibernate3.jar
* JBOSS_HOME/server/default/lib/hibernate-annotations.jar
* JBOSS_HOME/client/commons-logging.jar
* JBOSS_HOME/client/javassist.jar
* JBOSS_HOME/client/antlr.jar
* JBOSS_HOME/server/default/lib/jbosssx.jar
* JBOSS_HOME/server/default/lib/servlet-api.jar
* JBOSS_HOME/server/default/lib/jsp-api.jar
* JBOSS_HOME/lib/activation.jar (path changed since 4.2.0)
"jboss-ejb3.jar", "jboss-ejb3x.jar" and "jboss-annotations-ejb3.jar" contain the classes and annotations needed to code the EJBs.
"jboss-aop-jdk50.jar", "jboss-aspect-library-jdk50.jar" are required by the application client to start up.
The Hibernate jars are required to enabled the application client to catch Hibernate Exceptions (if not caught by server code), and are necessary for Hibernate development in an EJB project.
Another feature is that the "server configuration" is no longer a combobox but a plain text field. This way it is possible to enter any configuration other than "default", "minimal" and "all".
The plugin should also run with WTP 1.0, but I did not verify this.
Plugin overview and installation
With some small modifications I was able to use WTP 1.5 to develop a JEE5 enterprise application.
To use the plugin:
* JBoss 4.0.x: You MUST have installed the EJB3 RC9 to the default configuration so that the plugin can find all required libraries.
For JBoss 4.0.4 with installer including EJB3 RC8 this is done automatically.
For EJB3 RC 9 there is no JBoss AS installer, it must be installed to the default configuration manually. Later you can install EJB3 RC9 to any other configuration, the jars from the default configuration are only needed for starting up application clients and for Eclipse.
* JBoss 4.2.0: the default configuration must be present so that the plugin can find all required libraries (tested for CR1 to GA)
* JBoss 5.0.0: the default configuration must be present so that the plugin can find all required libraries (tested for Beta2)
* Delete previous versions of this plugin if already installed.
* Download org.eclipse.jst.server.jboss.ejb3_1.5.0.v200706052200.jar
* Copy the file to the subdirectory "plugins" of your eclipse installation.
* Restart eclipse once with the "-clean" option: "eclipse -clean".
* Create a new server runtime. You will find the runtimes in the "JBoss" branch, labeled "JBoss 4.0.4 or 4.0.5 with EJB3 RC8 or RC9", "JBoss 4.2.0" or "JBoss 5.0"
The plugin does not more than adding some additional JAR files to the project build path:
JBoss 4.0.x:
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-ejb3x.jar
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
* JBOSS_HOME/server/default/lib/hibernate3.jar
* JBOSS_HOME/server/default/lib/hibernate-annotations.jar
JBoss 4.2.0:
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-ejb3.jar
* JBOSS_HOME/server/default/lib/jboss-ejb3x.jar
* JBOSS_HOME/server/default/deploy/ejb3.deployer/jboss-annotations-ejb3.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aop-jdk50.jar
* JBOSS_HOME/server/default/deploy/jboss-aop-jdk50.deployer/jboss-aspect-library-jdk50.jar
* JBOSS_HOME/server/default/lib/hibernate3.jar
* JBOSS_HOME/server/default/lib/hibernate-annotations.jar
* JBOSS_HOME/client/commons-logging.jar
* JBOSS_HOME/client/javassist.jar
* JBOSS_HOME/client/antlr.jar
* JBOSS_HOME/server/default/lib/servlet-api.jar (in 4.0.x: "javax.servlet.jar")
* JBOSS_HOME/server/default/lib/jsp-api.jar (in 4.0.x: "javax.servlet.jsp.jar")
JBoss 5.0.0:
* JBOSS_HOME/server/default/deployers/ejb3.deployer/jboss-ejb3.jar
* JBOSS_HOME/server/default/deployers/ejb3.deployer/jboss-ejb3x.jar
* JBOSS_HOME/server/default/deployers/ejb3.deployer/jboss-annotations-ejb3.jar
* JBOSS_HOME/lib/jboss-aop-jdk50.jar
* JBOSS_HOME/server/default/deployers/jboss-aop-jboss5.deployer/jboss-aspect-library-jdk50.jar
* JBOSS_HOME/server/default/lib/hibernate3.jar
* JBOSS_HOME/server/default/lib/hibernate-annotations.jar
* JBOSS_HOME/client/commons-logging.jar
* JBOSS_HOME/client/javassist.jar
* JBOSS_HOME/client/antlr.jar
* JBOSS_HOME/server/default/lib/jbosssx.jar
* JBOSS_HOME/server/default/lib/servlet-api.jar
* JBOSS_HOME/server/default/lib/jsp-api.jar
* JBOSS_HOME/lib/activation.jar (path changed since 4.2.0)
"jboss-ejb3.jar", "jboss-ejb3x.jar" and "jboss-annotations-ejb3.jar" contain the classes and annotations needed to code the EJBs.
"jboss-aop-jdk50.jar", "jboss-aspect-library-jdk50.jar" are required by the application client to start up.
The Hibernate jars are required to enabled the application client to catch Hibernate Exceptions (if not caught by server code), and are necessary for Hibernate development in an EJB project.
Another feature is that the "server configuration" is no longer a combobox but a plain text field. This way it is possible to enter any configuration other than "default", "minimal" and "all".
The plugin should also run with WTP 1.0, but I did not verify this.
Comments