i added the job executor servlet to the jbpm-console.war. the servlet will start the job executor that is configured in the jbpm configuration. also i added the libraries jbpm-jpdl.jar and jbpm-identity.jar to the web console cause these were commented. david, what other way were they deployed in your environment ? in the build of the console, i would like all library dependencies to be packaged inside of the .war. that way, we get a portable standard java based .war console that could be deployed in a plain tomcat as is. Then in the enterprise subproject. i start from that .war and modify it's contents until i get an .ear file that can be deployed in a standard J2EE 1.4 server. also the ear file should is self contained. do you guys also think that this is an improvement ? 1 .war targetted for the standard java platform and 1 .ear targetted for a J2EE 1.4 appserver. david, i assume that you want to uncomment the servlet while you're developing. can you figure out a way to do this with a separate target in the console/build.xml somewhere ? you can have a look at enterprise/ear/build.xml for an example of how to comment out the job servlet with an ant script. i would like the default build target to keep the job executor servlet in the console web application. especially since the default targets will be used for automatic testing. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3982355#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...