On 2001.05.14 20:35:07 +1000 [EMAIL PROTECTED] wrote: > Hi to all, > Perhaps someone can point me towards the best approach for this: > > I have developed a relatively simple web app using a velocity > servlet > as the controller, and wish to migrate to using Turbine. > > I don't do anything special in my Controller velocity servlet, just > call > the appropriate object to build that screen. > ie I have 8 Command classes, one for each different screen I have. > Each classs will populate the context, and return the name of the > appropriate > template. > > Questions: > 1) By using Turbine, does this make the need for a 'custom' > Controller such as > my Velocity servlet redundant, or do I still need to override it to > implement > certain functionality? > By default, turbine provides you with a protocol for having your 'command' classes invoked prior to the velocity template parsing - e.g. if you have a screen template called FirstPage.vm, then a java class called FirstPage will be visited first. > 2) Does it still hold true that there will be only 1 screen that > will not have > authentication applied to it, as mentioned in the Turbine > specification doc. > (The 'Turbine and Velocity' document doesn't make any mention of > this ). Check out the sample application, where the Java screen classes derive from SecureScreen to ensure that validation has taken place before the screen is returned. In general terms, you can control whether zero, all, or some of your pages are authenticated. Maybe also check out the workings of the 'Login' elements (screen, layout, TurbineResources.properties, and turbine classes) in the demo app to get an idea of how it hangs together. > > I tried to run the example as given in the 'Turbine and Velocity', > but when > pointing my browser at > "http://localhost.localdomain:8080/servlet/Turbine/template/HelloWorld.vm"; > I get > a http 440 error. Is there anything special I need to do? > > Thanks in advance, > > Patrick Saunders. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
