Now I have to make up for chapter's reading experience because I think there is a place to mention.
When installing the configuration, it is described as follows:Jboss-3.2.1AndLomboz.21 _ 02, I decided to use JBoss 3.2.5 and lomboz 213. Although I am not clear about the new version features of JBoss, I think that since it can be upgraded, it has already solved the legacy issues. However, I am troubled by the configuration. Lobmboz 213 does not have the corresponding configuration file for JBoss 3.2.5, fortunately google help, find the 3.2.5 configuration file, download the 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/jbosssx-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 addition to this issue, I did not think that the author of this article even explained the eclipse bug, which is really responsible. Original reference:" 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 if you follow the picture in the article elsewhere.