I've been thinking of changing over to a search path for all these properties with the following order:
1) <property> in the application specification 2) servlet init parameter (web.xml) 3) servlet context init parameter (web.xml) 4) JVM system property (-D command line option) Using a search path is always nice, since you can then add new entries to the search path in some manner. -- [EMAIL PROTECTED] http://tapestry.sf.net > [EMAIL PROTECTED] wrote: > > > > No, JVM system properties are specified on the java command line, using > > the -D option. > > :-) ... I said I was lame. > It's working as expected now. > Somehow I got confused with the > "com.primix.tapestry.visit-class" property which is set in the *.application > file. > > Thanks, > > Luis Neves > > _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
