On Fri, 01 Sep 2000, you wrote:
> on 9/1/2000 5:53 PM, "John McNally" <[EMAIL PROTECTED]> wrote:
>
> > All the TemplateService does is keep track of the naming relationships
> > between templates and Screen modules, screen templates and the correct
> > layout templates, etc.
> >
> > The path property should be set the same for both. I was thinking the
> > TurbineTemplateProvider only allowed one path. But it seems from
> > discussions earlier it is able to handle multiple paths. I cut and pasted a
> > lot of code so maybe everything is working okay, I will look at it though.
> >
> > Other than that they coexist.
> >
> > John
>
> So far, I haven't been able to get the TDK up and running and it appears to
> be a few things related to finding out what the right path is:
>
> #1. The paths don't seem to work as relative paths to /WEB-INF/templates.
> #2. The WM system can't seem to create a log file.
>
Jon,
I haven't worked on the TDK for a little while so I'm not sure how the
setup handles this now. But, originally this was the reason for the
tdkhome variable in the newapp.props file. The tdkhome was set
to the full path of your TDK installation. This value would then get
picked up by the ant script and would set the full path in the appropriate
properties file (specifically the wm.props file) when you created a newapp.
Jason and I went back and forth as to whether it was needed or not. I felt
it was because it didn't appear that WM handled relative paths well. He
(Jason) can probably shed so light on how he got it to work.
--
dave
[EMAIL PROTECTED]
----------------------
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
