It is only necessary to make a place to mention it.
When installing configuration, the data is illustrated using JBoss-3.2.1 and Lomboz.21_02, I decided to use JBoss 3.2.5 and Lomboz 213. Although the new version of the new version of JBoss is unclear, I think there is no problem that I have already left. But I added trouble when I was configured. Lobmboz 213 has no corresponding configuration files for JBoss 3.2.5, but also Google Help, found 3.2.5 configuration file, download link http://www.kawaz.jp/pukiwiki/?plugin=attach&openfile=jboss325 .server & refer = jboss% 203.2.3% A2% AA3.2.4
The content is as follows:
Name = "jboss 3.2.5"
EjBModules = "True"
WebModules = "true"
Earmodules = "True">
Label = "Application Server Directory:"
TYPE = "Directory"
DEFAULT = "/ Your_server_root / appservers / jboss-3.2.5" />
Label = "Address:"
TYPE = "string"
DEFAULT = "127.0.0.1" />
Label = "Port:"
TYPE = "string"
DEFAULT = "8080" />
Label = "Server Configuration (Minimal / Default / all):"
TYPE = "string"
Default = "default" />
Label = "ClassPath Variable Name:"
TYPE = "string"
DEFAULT = "jboss325" />
Label = "ClassPath Variable:"
TYPE = "Directory"
DEFAULT = "/ Your_server_root / appservers / jboss-3.2.5" />
$ {serverrootdirectory}
$ {ServerRootDirectory} / server / $ {serverconfig} / deploy
$ {ServerRootDirectory} / server / $ {serverconfig} / deploy
$ {ServerRootDirectory} / server / $ {serverconfig} / deploy
Org.jnp.interfaces.namingContextFactory
JNP: // $ {serveraddress}: 1099
Org.jboss.main
$ {ServerRootDirectory} / bin
-c $ {serverconfig}
Org.jboss.shutdown
$ {ServerRootDirectory} / bin
-S
JDK_TOOLS
$ {classpathvariablename} /bin/run.jar
$ {classpathvariablename} /bin/shutdown.jar
$ {classpathvariablename} /client/jboss-j2ee.jar $ {classpathvariablename} /lib/concurrent.jar
$ {classpathvariablename} /lib/jboss-system.jar
$ {classpathvariablename} /lib/dom4j.jar
$ {classpathvariablename} /lib/xercesimpl.jar
$ {classpathvariablename} /lib/xml-apis.jar
$ {classpathvariablename} /lib/gnu-regExp.jar
$ {classpathvariablename} /lib/getopt.jar
$ {classpathvariablename} / server / $ {serverconfig} /deploy/jbossweb-tomcat50.sar/servlet-api.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/bcel.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jboss.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jboss-transaction.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jnpserver.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jpl-pattern.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jpl-util.jar
$ {classpathvariablename} /client/jboss-j2ee.jar
$ {classpathvariablename} /client/jboss-client.jar
$ {classpathvariablename} /client/jboss-common-client.jar
$ {classpathvariablename} /client/jboss-jaas.jar
$ {classpathvariablename} /client/jbossx-client.jar
$ {classpathvariablename} /client/jnet.jar
$ {classpathvariablename} /client/jnp-client.jar
$ {classpathvariablename} /client/log4j.jar
$ {classpathvariablename} /server/default/lib/jnpserver.jar
JDK_TOOLS
$ {classpathvariablename} /bin/run.jar
$ {classpathvariablename} /bin/shutdown.jar
$ {classpathvariablename} /client/jboss-j2ee.jar
$ {classpathvariablename} /lib/concurrent.jar
$ {classpathvariablename} /lib/jboss-system.jar
$ {classpathvariablename} / server / $ {serverconfig} /deploy/jbossweb-tomcat50.sar/servlet-api.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/bcel.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jboss.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jboss-transaction.jar $ {classpathvariablename} / server / $ {serverconfig} /lib/jnpserver.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jpl-pattern.jar
$ {classpathvariablename} / server / $ {serverconfig} /lib/jpl-util.jar
In the process of the configuration, in addition to this problem, the author of this article did not think of Eclipse's BUG, it was responsible. Original quote: "
NOW Click On Libraries Tab on The Project Creation Wizard. Because of a bug in Eclipse 2.1 this library is configured Wrongly. So select this library and remove it.
There is no problem in other places, according to the article, there is no problem.
