Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: domain of ap-cocoon-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: dev@cocoon.apache.org
From: oceatoon <t.katelbach@systheo.com>
Subject: Re: Multiple forms on one page
Date: Mon, 22 Nov 2004 15:32:29 +0100
Organization: oceatoon
Lines: 44
Message-ID: <cnssmv$l31$1@sea.gmane.org>
References: <41A1AFAB.5090802@upaya.co.uk> <41A1BB87.9090207@apache.org>
 <1101119094.6532.28.camel@yum.site> <41A1C192.7050604@apache.org>
 <1101120467.6532.32.camel@yum.site>
Reply-To: t.katelbach@systheo.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7Bit
Mail-Copies-To: t.katelbach@systheo.com
User-Agent: KNode/0.8.0
Sender: news <news@sea.gmane.org>

Are there any docs on this?
or use cases ?
We have done a solution where we have one huge form model, and then the
template is devide in multiple tabs ,It all works great but now we're
trying to structure the validation system (freshly speaking)
This MultiForms might be the solution to our problems :)

Best Regards
Tibor

Bruno Dumon wrote:

> On Mon, 2004-11-22 at 11:38 +0100, Reinhard Poetz wrote:
>> Bruno Dumon wrote:
>> 
>> >>I think one problem is our flowscript API:
>> >>
>> >>  var form = new Form("...");
>> >>  form.show("mypipeline", bizdata);
>> >>
>> >>This way you can only show one form a page. Maybe we can do somethink
>> >>like
>> >>
>> >>  var multiform = new Multiform({form1 : form1, form2 : form2);
>> >>  multiform.show("myMultiformPipeline", bizdata);
>> >>
>> >>The next step would have to be an enhancement of the forms transformer
>> >>because it would have to render more than one form. This would probably
>> >>require a unique id in the forms template. This id needs to be the same
>> >>as the id used in "new Multiform(...)".
>> > 
>> > 
>> > The forms transformer can handle this, the ft:form-template element can
>> > have a location attribute containing a jxpath expression that points to
>> > the form object.
>> > 
>> 
>> What's the object this jxpath-expression is used on?
> 
> the flow context, and with a few variables declared (request,
> session, ...). See FormsPipelineConfig.createConfig where the jxpath
> context is created.
>