I hope that there is not a VelocitySiteScreen. I am pretty sure I did not
create one. It should be VelocityScreen.
The Site fragment was added early on in the template integration to distinguish
from the more standard (at the time) style of mapping Screens to templates
(hardcoding the template in the Screen). There is no reason to separate these
two scenarios anymore, at least at the base Screen level that comes with
Turbine. It should be dropped altogether. I have just been reluctant to change
it for WM since it will break people's TR.props. Of course these get broke all
the time, so if someone else wants to rename things, go for it.
Yes you need the appropriate template engine service enabled.
John McNally
Simon Hay wrote:
>
> Hi,
>
> I've installed the TDK and (finally) got it all running; I'm now
> attempting to start to develop an application using the Velocity Site
> stuff. When I follow the tutorial, though, and write Helloworld.java
> which implements (or extends, can't remember now) VelocitySiteScreen,
> the compiler complains that it can't find VelocitySiteScreen. Neither
> can I - as far as I can see it's not in any of the JARs etc. Where is
> this elusive class supposed to live!? :-)
>
> Also, do I need to have the TomcatVelocityService enabled for this all
> to work?
>
> Thanks very much,
>
> -Simon
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
