Hi Peter, I'm glad hearing from you.
> > when do you think that Turbine 2.4 will be released? > > > I think Eric wanted to finalize something on the pipeline data issue > which was discussed on this list a few weeks ago. On a recent visit to > the UK Eric and I got together and did some refactoring in preparation > for this but it is probably down to me to finish it and put a proposal > forward. I'm buried in deadlines, but I will try to help move it > forward. > > Really, it should not be long. If there is anything I can help tell me. Maybe I can provide some documentation, bug reports or test cases. We started to use EasyMock for testing the servlet container dependent stuff and if this is for interest let me know. > I am pretty sure that you can add what you need but you may need to > modify/add to the manager classes in fulcrum security. Eric > could answer > this one better... Okay I hope he reads this list to. Using versioning in high concurrent environments is really recommend when using hibernate (btw hibernate is not the only ORM tool using versioning to solve the optimistic locking problem). There is also some room for caching which sould be considerd. > Validation can be added at any point in development by adding > validation > directives to the .xml files and reloading them. > > The validators used can be custom written, can leverage > commons-validation, use oro regex or jdk 1.4 regex or other types of > validation. Great Job Peter! Doing thing in a declarative way is very convenient. Cool! > The current version is designed to use the pipeline in T2.4. However, > the original version is currently in use in production using > T2.3 and a > custom ParameterParser. A colleague is this week testing the newly > updated ReviewParameterParser for the latest version against a release > version of Turbine 2.3. > > As soon as this is done, I'll ask Eric to commit it into proposals. Could you please post a announcement to the list if its is availabe? Would be cool! We want to start developing with turbine 2.3 in a new project. Using your validation framework would be great. When will it be available? > As for using Spring, my feeling is that unless there is a very good > reason not to we should stick with an Apache solution as default. > Turbine can use Torque, OJB, Hibernate etc. but these are not > central to > Turbine. The Service Framework is what Turbine is and I think the > default should be Apache if possible. Agreed. It would be great to keep Turbine reuseable e.g use the Web Framwork Turbine togehter with Spring. Using Turbine with Velocity avoids the XML hell others introduce and I'm really happy about this. > I see no reason why someone should not > put forward a Spring, pico or other framework providing > service as well. Cool! > I think that it was Alex Karasulu who wrote a good piece > about wrapping > components to work in different containers, I think it was in the > Directory project pages. Maybe we should look at this more closely. Interesting. I will look into it. But maybe it would be sufficent to provide a simple SpringCompononentService somewhere? Mabye you can consider to release Turbine in similar fashion the Spring team does by spliting the project into smaller jars. What do you thing about this suggestion? Thx Toby -- tobias rademacher [sofwareentwickler] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
