I think app-workflow is the way to go. From what we heard from John Howard ( who is working with Jeff) app-workflow has some real neat features like a GUI tool to establish the initial design and flow. Also it is pretty easy to use I think.I am starting to look at using Jeff's excellent work on app-workflow (if you haven't checked it out yet, read the doc in app-workflow/tutorial).
One thing I noticed is that the workflow definition file (workflows.xml) needs to be in the classpath, and Jeff has added the capability to automatically do this if the file is put in app-workflow. This got me thinking, would it make sense to change our build scripts to put *any* non .java files in the src/java package hierarchy to be automatically copied to the build/classes directory, and then included in the JAR? This would include .properties files as well. This is exactly what Eclipse does, BTW.
This is a good idea absolutely. But with Eclipse running on Linux the Java code still cannot load the properties file from the jar.
I faced some serious problems and had to specify the path to the properties files as System variables in Tomcat. This always required some code changes in some of the packages( iText pdf generator for example) we are using.
http://keelframework.org/documentation Keelgroup mailing list [EMAIL PROTECTED] http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
