To properly answer your questions, I decided the best was to try and run a JBoss instance as a JPPFTask.
It almost works. I'm still having issues with the web services components (probably forgot some configuration parameters), but it appears that the rest is working properly. I could see that the web server, EJB container, JMS, JDBC, JCA connectors are all started and deployed properly and I was able to play with the web and JMX consoles.
To achieve this with JBoss 4.2.2, I had to perform the following:
- some reverse engineering (as permitted by the JBoss LGPL license, using the source code is really helping!) to figure out which JBoss class to start and what configuration properties to set
- add the proper JBOSS libraries to either JPPF client, server or node's classpath (i.e. jars in JBOSS_HOME/lib, JBOSS_HOME/lib/endorsed, JBOSS_HOME/server/<server_config>/lib)
Where you set this classpath has a significant impact on how long it takes for JBoss to startup
- I had to modify the JPPF class loader to ensure that java packages are defined - see ClassLoader.definePackage()
. In effect JBoss checks that its packages are defined by the class loader, and if not, it will fail at startup. This modification is currently only available in the JPPF CVS trunk, and not part of any distribution.
- JBoss must be installed on the same machine as the node, or at least on a file system it can access, as it relies on a specific file structure
For your information, here is the code for the JPPF task I used:
* This task runs an instance of JBoss.
public class JBossTask extends JPPFTask
public void run()
String path = "C:/Tools/jboss-4.2.2.GA";
URL url = new File(path).toURI().toURL();
Properties props = new Properties();
Server server = new ServerImpl();
In conclusion, I believe what you seek would is possible, provided we can resolve the last hurtles in the JBoss startup process, but I'm quite confident that it's only a matter of time.
I'm interested in your feedback on this, I think it's an interesting approach and it may open many horizons for JPPF.