Hi peter, Currently I'm using the rundata object to fetch the users active Session, and saving the hibernate Query object along with parameters required for re-executing the search. So if I'm not going to use rundata anymore, where will I get the user's session from? Or are you saying I should make some sort of this new valve and add it to the pipeline? Any strategies as to how pagination is done the smartest way in this system is welcome.
Sounds great, so I should be able to port the project without any problems besides the few rundata specific. /Martin -----Original Message----- From: Peter Courcoux [mailto:[EMAIL PROTECTED] Sent: 15. januar 2005 00:38 To: Turbine Users List Subject: RE: Duplicate Parameter in Validation.xml file :template.index.vm.template Martin, RunData is an interface for the object used to transfer data along from the http request to the response. In turbine prior to 2.4 that process was largely turbine defined and to a large extent a fixed sequence. RunData is a horrible interface with highly coupled specific methods suited to its original purpose. In turbine 2.4, a pipeline has been implemented to handle the processing of the request through to the response, and "valves" are used to handle the same sequence. See the turbine-classic-pipeline.xml file in conf for 2.4. This is now customisable and a new mechanism was needed to enable the moving of data along the pipeline from valve to valve and which is flexible enough to handle custom valves. The whole mechanism is backwards compatible but many of the methods using RunData are deprecated and the intention is to work to eventually remove it completely. RunData is currently saved in pipelineData and extracted where needed. Turbine 2.4 works the same as 2.3 without the zebra workflow engine. I hope that this helps. Don't hesitate to ask more questions. Peter On Fri, 2005-01-14 at 23:07 +0100, ANSI Webmaster wrote: > Hey, > > Ah that's great, if you'll post when you have updated the files I'll check > it out. > > I have researched a bit on the flow control, it seems nice for some uses but > I highly doubt I'll have use for it in my "community system". Will the pages > appear as they have prior to that version by using the > SecureScreen/VelocityScreen, or what is needed to disable it so it works > like before? > > I see some warnings for RUNDATA, that it is deprecated - what is replacing > it? Currently im using rundata to store for instance a Query object and > arguments for it in there for pagination in say a search result. > > Thanks > /Martin > > -----Original Message----- > From: Ben Gidley [mailto:[EMAIL PROTECTED] > Sent: 8. januar 2005 11:21 > To: Turbine Users List > Subject: Re: Duplicate Parameter in Validation.xml file :template.index.vm > .template > > Hi, > > Aarrgh - I think is the correct statement. > > A simple explaination is that the Antelope is generally created by > taking the bits we want to open source from much bigger Anite > applications - now those missing files are sat in the other > application. I am quite busy and won't have time for a few days to > sort through and locate them and fix it all. > > On the back button. This is a trick we have added to turbine to let us > control the back button. What happens is if you press back the > SessionValidator detects this and redirects you back to the task list. > The reason you would want to do this it in workflow a screen submit > can trigger another user doing something - so you can't go back cos it > will often be too late. You can disable this behavious per page if you > want. > > On Why workflow is useful. Firstly it is not useful at all and just a > pain if you are doing read-only data display. > > If however you are doing a process where the user does A then B and if > it is sunny do D if raining do C and D etc, it control the flow. The > GUI designer lets you model the flow as a chart in front of the users. > Then the app picks it up. You then implement each screen. > > Also workflow gives us some toys such as > - A Pause Button on each form that let us save unvalidated data can > come back later > - Ability to assign tasks to users, groups of users, set permissions > on a row level dynamically > - A PropertySet which works like a HTTPSession but lasts forever and > is persisted in the DB (using serializable objects - or if you don't > mind the performance hit you can plug in XStream). > > Workflow is only really useful for systems with a lot of state. > > Ben > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Peter Courcoux <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
