Public stuff

WTP 3.0: JBoss JSR88 and exploded deployment / Server definition for JBoss 5.1, 6.0, 6.1 and 7.1

Features for JBoss 4.2 to 7.1: JSR88 deployment

Server definition for JBoss 7.1 in "standalone" mode:

• Copy file to "standalone\deployments"
• Wait until a deployment marker file ".deployed" or ".failed" is created.

• Delete deployed file in "standalone\deployments"
• Wait until a deployment marker file ".undeployed" is created.

Features for JBoss 5.1 to 6.1: Exploded deployment

Enhancements for JBoss 4.2 to 6.1

1. Endorsed dirs (see http://docs.oracle.com/javase/6/docs/technotes/guides/standards/index.html): for all server definitions up to JBoss 6.1 (JBoss 7 does not seem to support this), "lib/endorsed" is added to Classpath. The VM argument "-Djava.endorsed.dirs="${serverRootDirectory}/lib/endorsed", which is missing in the WTP 5.0 definition, is also added (this does of course NOT modify the WTP server definitions). Follow this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=250643 for the core libraries.
   
   
2. For JBoss 5.1, 6.0 and 6.1, there are five differences to the WTP default server definition for 5.0:
   
   • (only JBoss 6.x definitions) support for the new JavaEE6 project facets of WTP 3.2 (Eclipse 3.6). Of course not supported in previous WTP versions.
   • This server definition adds the libraries required for the new WebBeans support.
   • Default startup timeout was increased from 50 to 180 seconds
   • JBoss 6.1.0: the server requires a new VM argument:
     -Dlogging.configuration=file:"${serverRootDirectory}/logging.properties"
     See this forum thread: http://community.jboss.org/thread/167106
   
   
3. Shutting down servers with non-default port configuration:
   
   JBoss up to 6.0.0M2:
   If the JNDI port of the server is changed, shutdown will fail. See http://www.eclipse.org/forums/index.php?t=msg&goto=489439 for discussion and solution for this issue (not that "-S" changed to "-s ...". Case matters...).
   All my server definitions contain this modified shutdown ant task:
   

   	<stop>
   		<mainClass>org.jboss.Shutdown</mainClass>
   		<workingDirectory>${serverRootDirectory}/bin</workingDirectory>
   		<programArguments>-s jnp://${serverAddress}:${jndiPort}</programArguments>
   		<vmParameters>-Djboss.boot.loader.name=shutdown.bat</vmParameters>
   		<classpathReference>jboss.shutdown</classpathReference>
   	</stop>  

   
   JBoss 6.0.0M3 to 6.1:
   In this version shutting down the server was changed: it is no longer a JNDI call at port 1099, but a RMI/JMX call at port 1090, and the URL is "service:jmx:rmi:///jndi/rmi://localhost:1090/jmxrmi". Thus, a new config parameter "RMI/JMX port" with default = 1090 was added. The ant task now looks like this:

   	<stop>
   		<mainClass>org.jboss.Shutdown</mainClass>
   		<workingDirectory>${serverRootDirectory}/bin</workingDirectory>
   		<programArguments>-s service:jmx:rmi:///jndi/rmi://${serverAddress}:${jmxRmiPort}/jmxrmi</programArguments>
   		<vmParameters>-Djboss.boot.loader.name=shutdown.bat</vmParameters>
   		<classpathReference>jboss.shutdown</classpathReference>
   	</stop>

   See https://community.jboss.org/thread/152911 for some more links.

Requirements

Installation

Usage

Internals

   <category name="org.jboss">
      <priority value="TRACE"/>
   </category>

	<extension point="org.eclipse.wst.server.core.serverTypes">
	     ...
	     <serverType
	           runtime="true"
	           class="org.eclipse.jst.server.generic.core.internal.GenericServer"
	           id="org.eclipse.jst.server.generic.jboss5"
	           ...
	           hasConfiguration="false"
	           startBeforePublish="true"
	           launchModes="run,debug,profile">        
	     </serverType>
	</extension>