On 09.Jan.2003 -- 09:18 PM, Ivelin Ivanov wrote:
> > > > From: "Christian Haul" <[EMAIL PROTECTED]>
> >
> > > > If no validation is required, and only the XForms -> HTML conversion
> > > > is needed, a complete XMLForms instance is needed, still. Would it be
> > > > possible / OK to remove the dependencies of the XMLFormTransformer
> > > > from Form? As far as I could see, all it does is lookup the Form and
> > > > use the getVale() method.
> > >
> > > Can you give me an example where "only the XForms -> HTML conversion is
> > > needed".
> > > I am not sure I understand what that means.
> >
> > This happens when you want to profit from the XForms features of
> > detatched instance data but have next to none result processing. Say,
> > you have an XML representation of your form data. This could be
> > generated by an XMLizable object, a <esql:get-columns/> tag, or
> > another processing pipeline.
>
> I can see how you might use another source for the document and not need the
> XMLFormTransformer at all.
Mmmh, doesn't the XMLFormTransformer do the XForms -> HTML conversion
i.e. fill in all the values and handle repeat elements &c.?
> Instead some of the new transformers might be used.
Actually, a combination of the two SimpleForm*Transformers do what I
want. The InstanceExtraction part creates a DOM stored in a request
attribute and the other transformer uses the form element's name as
XPath-Expression to the DOM. Works like a charm :-) -- but only for
HTML form elements, not XForms :-|
> Let me clarify the scenario though:
>
> 1) Say you have a document extracted from ESQL
> 2) You also have an XForms document which refers to elements in the document
> 3) Now, who will be responsible for resolving the references to 1) in 2)
Since XMLForms operates via the model through XPaths, I think of 3a)
extract the instance data to a DOM and 3b) have the XMLFormTransformer
use that instead of a Form.
> 4) Then, when the browser posts the HTML form, what component will update
> the underlying data model (SQL database for example)?
This is optional. XForms can be used for display only. Another
possibility is to create an XML document from the parameters and store
just that.
One application is to store the entered data in a database (XML
database or a CLOB column in a RDBMS), store the form to enter, edit
and display that data in another database (other table).
Another reason for the request to loose the coupling between the
XForms to HTML conversion and the XMLForms framework is to be able to
experiment with other backends. Certainly, this, XForms -> HTML, is
needed with all approaches. But validation, processing esp. in
relation to flow script is still discussed.
Chris.
--
C h r i s t i a n H a u l
[EMAIL PROTECTED]
fingerprint: 99B0 1D9D 7919 644A 4837 7D73 FEF9 6856 335A 9E08
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
