On Mon, Oct 08, 2001 at 03:04:24PM +0200, Jacopo Cappellato wrote: > Hi Jozsa, > > maybe you have to set up correctly the module's classpath in > TurbineResources.properties file: > > ...... > # ------------------------------------------------------------------- > # > # M O D U L E P A C K A G E S .. > # Default: org.apache.turbine.modules > # ------------------------------------------------------------------- > > module.packages=org.dyn.joint.modules,org.apache.turbine.modules
I have it exactly like this already. I've started my application using the testapp, and it filled out this for me; so I think that's not the problem in my case. That raises an other question, which I wanted to ask anyway: the default 'testapp' application and derivates (which use the tdk/build.xml to generate the starting files) dont use a separated source and build directory structure. Nor the generated WEB-INF/build/build.xml has support for 'deploy' and 'dist' targets. I've started learning Turbine using the Tomcat Application Development Guide (1), which showed a very clean way of development, using a separate source directory outside of the webapps dir, and the deploy target to move the binaries and needed support files to their final location. When I've finished this tutorial, I moved on experimenting with Turbine's testapp, and found the 'stuff-all-sources-and-binaries-together' concept very confusing. Is there somewhere a sample build.xml file which both uses Turbine, and uses the Tomcat-way of file organizing, with a deploy ant target, which moves the only things to webapps which are actually needed for the application? I know I could write one myself, but as a newbie I'm not that skilled yet. Christopher (1) http://jakarta.apache.org/tomcat/tomcat-4.0-doc/appdev/index.html -- .Digital.Yearning.for.Networked.Assassination.and.Xenocide --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
