We thought we could have released dynamic website based on turbine for our customers in 2 months. Could not get turbine working in 1 month. Had to change to annother product to get finished on time.
We tried TDK 2.1. I liked the idea of almost everything. Sample app worked kind of OK. I generated extra files for our project using vm- templates in torque like: skeleton intake.xml based on our project schema.xml and lots of other helpful code. Problems started at intake service. According to my opinion even intake.xml format was incorrect for that version and then we got tons of exeptions. Seemed that there were not only wrong files but wrong *.jar versions of xml parser according to mail archives etc... Since this was out of the box TDK 2.1 "production release" dozens of people around the web are loading it and going trough the same misery over and over again figuring out what's wrong with the release... things that one experienced TDK 2.1 user could have fixed in the release. I aggree to what has been said about getting the feeling about the product how it makes life easier and more interesting on triming things and such on. (I used the product to a degree) On the other hand... in the real world, when payment depends on weather customer receives their application or not... there is no time to chase bugs caused by disinterest in release quality. - Pauli -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
