* "Henning P. Schmiedehausen" <[EMAIL PROTECTED]> wrote:
|
| >3) servlet container is housed in the TDK
|
| -1
|
| I'd prefer "servlet container is housed somewhere else". I e.g. run a
| standard apache/tomcat setup and I simply adjust pathes in there.
|
[snip] and then...
| >4) all sql is generated by the TDK, even test data could be
| > handled by an XML config and Torque would generate the
| > inserts for the target database.
|
| I'd like to vote -1 here but I am open to good arguments. ;-)
|
| I e.g. develop my turbine apps right from the Turbine CVS archive. No
| TDK involved at all. I don't want to get locked into the TDK at all (I
| consider it diametral to my way of working. ;-) )
|
Well, if you don't use the TDK then you shouldn't be to worried about
what goes the TDK - right ?
I like that the TDK is self contained and includes a servlet container.
That is after all the purpose of the TDK, to let new developers get
up and running with Turbine quickly.
--
Gunnar R�nning - [EMAIL PROTECTED]
Senior Consultant, Polygnosis AS, http://www.polygnosis.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
