Hello Intake Wizards! :-)
We are using Intake (or trying to) in our web application that is Jetspeed-based, and therefore has Turbine, Intake, etc for free because they come with Jetspeed... We are trying to understand how to properly use Intake for data validation. The basic problem we are having is that there does not seem to be any way to 'carry forward' Intake data from one request to another, or from one page to another. For example, how about a form that you fill in a few fields, and submit it, and then a 'form' Action class wants to save the data you submitted into the session and redirect you to a different URL where a 'view' Action class will pull the saved data out of the session, and put it into the context so that a velocity template can render it. Problems that come up include... * We tried saving the IntakeTool itself from request to request, since it contains the Groups & Fields, but the Pull service wants to recycle it after each request so it works once and then the data goes away * We tried to pull our intake Group out of the IntakeTool and carry that forward, but IntakeTool.removeGroup() recycles the Group, which blows the data away Our last idea was to make a business object and do the mapToObject/setProperties thing, but that craps out when a form is submitted with invalid data, because formGroup.setProperties(bizObj) throws an exception when trying to set the values from formGroup into the bizObj. So. Has anybody figured out how to use Intake with a lifespan of longer than a single request? Thanks!!! Pat, Erich, et al -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
