On 7/25/01 5:18 PM, "John McNally" <[EMAIL PROTECTED]> wrote:
> Gunnar R�nning wrote:
>>
>> * "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.
>>
>
> I think the point is (for example): do not make developers who use
> turbine outside the tdk have to use the tdk to generate such things as
> the sql for the security classes which are part of turbine. Since
> torque is being split into a seperate project and the security stuff
> will be in fulcrum, I would say that fulcrum would need to use torque to
> generate the classes/sql and this should be self-contained. fulcrum
> should not rely on the tdk being present.
Yes, Fulcrum should be self contained. Using turbine, fulcrum, or
torque will never rely on the TDK being present, I don't know
where that idea came from. If you look at what's present in the fulcrum
repository you will see the targets for generating the security classes
are there already.
I want to promote the TDK as the standard way of developing turbine apps and
as such the TDK will house the targets to generate everything a turbine app
needs. If a project wants to do it their own way, than they can use torque
in stand-alone mode and replicate the functionality provided in the TDK.
I don't have any problem with that, but I think eventually this will
be seen as a waste of time. The TDK by no means has everything a project
needs right now, but I still think working together on a common
development process is better than every project doing their
own thing. But this doesn't preclude any project from doing their
own thing.
>
> john mcnally
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
