Maybe I just something overlooked in the IDE, googled the wrong tag no idea: When changing the JBoss server configuration is not (for me) of the Eclipse classpath is set correctly. The following my no workaround ...
following data:
Eclipse Ganymede 3.4.1 (with WTP)
Actually, I just wanted to "experiment" with something JBoss Cache, more about in another blog entry. However, the libraries required for this purpose only in the JBoss
contain all Configuration (JBoss 4.2.3 by default minimal
default
and
- be said
- default, what else is the default).
Step 1: Server Configuration starts in the mode of the server, you can make in the Server Properties. Simply in Eclipse on the Server tab - , JBoss and select press F3. In the section Server
Properites can choose next to Address, port, and JNDI Port and the Server Configuration - . Here, then, for example, can all be selected (or a custom configuration).
- Step 2: Project Classpath Subsequently, however, the classpath in the Eclipse projects (eg test (ß EAR project), TestEJB, TestWeb) still default. JBoss libraries in the classpath are still using the old '
default setting ( $ JBOSS_HOME / server / default / lib ). Thus, the more libraries are not available in the class path, like something the JBoss Cache jar files.
I have this hammer out only following intervention in the WTP Server JBoss Plugin:
In JBoss 4.2.3 GA so
The classpath can be adjusted to where you just in the file all / default / with / \u0026lt; new configuration> / such as economies
/ all /
(a backup copy of harm before the change not sure ;-))
Then start Eclipse again, clean but with the option (this in the console in the directory $
eclipse-clean call) #############
It is natural also possible to create a completely new server, so that for example, between the servers JBoss 4.2.3 (default)
and JBoss 4.2.3 (all) can choose
However, I personally like to have a fan per project not only its own workspace, but also its own Eclipse. Thus, the Eclipse plug-ins to be tailored to the project in and inevitably times for new projects to benefit from a more recent version of Eclipse. one has its own Eclipse project for each, then there can be even "wild" change the original configuration - As described above ;-)