RE: [FormProc-developer] FormProcService

[Anthony E. <me...@an...>]

> -----Original Message-----
> From: for...@li... 
> [mailto:for...@li...] On 
> Behalf Of Ken Keller
> Sent: Sunday, June 02, 2002 6:30 PM
> To: Anthony Eden; FormProc Developer List
> Subject: [FormProc-developer] FormProcService
> 
> 
> I looked at your CVS.
> 
> So the idea is to have Turbine create a 
> TurbineFormProcService instance & call init() which creates a 
> FormManager once.
> 
> You call:
> HttpForm aForm = formProcSvc.createForm(name, target);
> The service binds the FormManager for you.
> 
> Does this make the svc available to Velocity as $FormProc?

No.  I did not write the "pull" part of the service yet.  I am not
completely familiar with how Turbine works so a lot of this is new for
me.  Once I do I imagine I would like to be able to expose the Form
object as $form (or perhaps have some way to name the form, i.e.
$myForm1 or $myForm2...but perhaps that isn't necessary or even
possible).

> Even if it did, I don't think it can be used from Velocity 
> screens without either putting various collections into the 
> Context such as: $formFieldResults $formFieldGroupResults 
> $formFieldMessages or adding more methods such as:
> $form.getGroupErrorMessages()
> 
> Am I missing something? -Ken

Well, if you have a Form object and you call form.process() with the
HttpServletRequest then the results are in the FormResult object.
However none of this is exposed in the context.  Like I said up above I
still need to work out the "pull" part of the service.

Sincerely,
Anthony Eden