>Christian Haul wrote: > >Hi all, > >I've spend some time now understanding XMLForm and I have looked at >the popup sample from Michael >http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15100 >
Hi Christian, thnx for looking at the sample. >I couldn't find a post from Josema Alonso regarding XForms & Xindice >that appeared related. Ivelin, which one do you have in mind? Could >you send me a link or a copy? > >Indeed, the Popup sample has a similar edge to my whish to make a form >on the fly from XML. > >Michael's WriteDOMTransformer does a fairly similar job as the >SimpleFormInstanceExtractionTransformer. Only that the latter already >uses OutputModules and has a slightly different default configuration. >(To be honest, it is based on the WriteDOMTransformer from 2.0.x, >which changed significantly in 2.1. A similarity is hence not >surprising). If possible i'd prefer a transformer that's not neccesarily bound to xmlform. Would it be possible to make your transformer more general? > >Together with the XmlFormPopupAction it is possible to create a form >on the fly. Great! > >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. > I wasn't able to put the xmlform data only in the request. I'd prefer not storing the data for the xmlform in the session but in the request for single form handling. >OK, there's violations and modelReferenceForView so that would be >difficult. Perhaps two transformers, a minimal one without this and >another one including violations and the modelReferenceForView? > >Thoughts? > > Chris. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
