On Wed, 2002-05-15 at 11:14, Godwin Ko wrote: > If I create a screen class named Default.java at the top screen level then > all template files that with no screen class defined will use this default > screen class, is this the default behavior of turbine 2.1? I'm a little bit > confuse about the java screen binding with template. The template search > sequence has been documented in Velocity Site howto but is the screen class > search sequence the same as template? > > Godwin Ko.
I'm also tinkering with tdk/turbine 2.1 trying to understand how it all works. I don't feel like I understand it quite well enough to try and give you a definitive answer, but one thing I've found helpful is that Turbine looks for classes in much the same way as Java searches the CLASSPATH. If your TurbineResources.properties file specifies module.packages=<my.packages.path>,org.apache.turbine.flux.modules, then turbine will search in my/packages/path for class files before searching in the org/apache/turbine/... path. What I did was to copy the standard VelocityPage and VelocityECSLayout from the org/apache directories into my own directory tree, renamed to MyVelocityPage.java and MyVelocityECSLayout.java. Then I modified the TR.props file to point to MyVelocityPage and MyVelocityECSLayout instead of the originals. A few System.out.println's, and I could watch the program code scroll by as my web pages loaded. For some reason, all my screens seem to wind up calling FluxScreen.isAuthorized() at some point--not sure why. But anyway, maybe this will help you trace your own code. Turbine is a bit tricky to follow if you're trying to step through the code by eyeballing it. Mark [EMAIL PROTECTED] My horoscope says today is a bad day to be superstitious. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
