pipeline input to page, failure of xforms to html

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

pipeline input to page, failure of xforms to html

Smith, Donald

We have our pipeline set up and working for our page, so that the result of the pipeline is fed to the view:

 

<page id="newXMLEditorTE" path-info="/toolEvaluation/newXMLEditorTE" model="../ToolEvalApp/newXMLEditorTE/wscall.xpl" view="../ToolEvalApp/newXMLEditorTE/view.xml">

 

We are sure that the result of the web service call is populating the page, but now none of our xforms controls are showing up. Looking at the HTML source, we see that the xforms controls in the view are coming over to HTMl without being transformed into HTML form controls. Our HTML document now has a bunch of xforms controls in it.

 

The view worked fine as long as we had a static “form”, but as soon as we got the web service pipeline working, no more control conversion.

 

What are we missing about how the process works?

 

Thanks,

 

Don



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: pipeline input to page, failure of xforms to html

Erik Bruchez
Administrator
Smith, Donald wrote:

> <page id="newXMLEditorTE" path-info="/toolEvaluation/newXMLEditorTE"
> model="../ToolEvalApp/newXMLEditorTE/wscall.xpl"
> view="../ToolEvalApp/newXMLEditorTE/view.xml">

Sounds good.

> We are sure that the result of the web service call is populating the
> page, but now none of our xforms controls are showing up. Looking at the
> HTML source, we see that the xforms controls in the view are coming over
> to HTMl /without/ being transformed into HTML form controls. Our HTML
> document now has a bunch of xforms controls in it.
>
> The view worked fine as long as we had a static “form”, but as soon as
> we got the web service pipeline working, no more control conversion.
>
> What are we missing about how the process works?
They key for XForms processing to take place is to have a document in
the XHTML namespace, and at least one XForms model under
xhtml:html/xhtml:head. Other than that, there is should really not be
anything else to it!

-Erik



--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws