Hi, I have made a branch called "rundata_security_changes" where I am going to start the RunData changes. Gonzalo and Dan, this is where we will work until the default security implementation works with our new plan.
When this is finished I will merge all our changes back into the trunk. Once I'm finished the RunData changes the test bed will still work but applications using t3 and the current security mechanism will be broken. So I'll make the RunData changes and then you two (Gonzalo and Dan) can take a bit of time to work out exactly what you think is best. Once I'm done the RunData changes I'm going to move on to cleaning up the view system. I was chatting with Jeff yesterday and I think the next thing to tackle on a first pass is development methodology. The CVS model of the TDK works pretty much like Scarab but I would like to clean up the torque stuff, add some cactus testing for the client side and introduce some continuous integration techniques using Maven. Right off the top of my head I can see a couple simplifications in the TDK: 1) The only mode for generating an app will be CVS mode which looks very close to what scarab does. 2) Will allow the TDK to work with an already installed version of a servlet container 3) Add the auto jar updater functionality to deal with non-jar resources so the TDK can become versionless and a simple task will update the TDK when new resources are available. That's it for now. -- 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: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
