XForms/JSF Form Submission

Hello Alessandro,

Thursday, May 24, 2007, 11:39:37 AM, you wrote:

> On 5/23/07, BitByter <[hidden email]> wrote:
>> > Do you have the ops-xforms-filter mapped to *.faces in web.xml, as
>> > described in the page below?
>> >
>> > http://www.orbeon.com/ops/doc/reference-xforms-java
>>
>> No, the ops-xforms-filter is mapped to /xforms/* in my web.xml, and the
>> Demo.jsp page is located beneath this folder. All my other samples in the
>> same directory get processed by the filter.

> You mentioned earlier that the request goes to a page with the .faces
> extension. So:
>
> 1) The request is made to /xforms/Demo.faces
> 2) The JSF servlet handles that request and runs Demo.jsp
> 3) The output is HTML + XForms
> 4) This output is processed by the Orbeon Filter
>
> Is this what you expect to happen?


Yes, this is what I basically expect to happen.  :)


>> I guess you don't have time left to check whether you can get that demo
>> application to run, respectively just get it to be processed by Orbeon
>> Forms (in a seperate deployment)?

> That's right. There is only so much time we can spend on the list :).

Sometimes a day should have 48 hours or more...  :)

- bitbyter





--
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

Hello Erik,

Wednesday, May 23, 2007, 5:31:07 PM, you wrote:

> * Orbeon Forms also create a top-level <form> element.
>
> * But contrary to JSF (unless Ajax is used in JSF), Orbeon Forms only
>    rarely submit that form. In fact, it does it only when performing
>    submissions with replace="all". In all other cases, it uses Ajax to
>    communicate with the server.

> Just pointing out that there are opporturnities for clashes between
> the two systems.

There should be no clashes as long as JSF and XForms value bindings is not
mixed up, like referencing a managed bean property within XForms instance
data, eg like this:

<instance id=data>
   <myData>
      <value>#{myJsfBean.value}</value>
   </myData>
</instance>


 >> All form data is being updated after successfull validation at the
 >> managed bean(s) to which each form data is bound. Based on the the
 >> ID of the button, the JSF framework knows which action handler to
 >> call to handle the request. The result of the action handler is used
 >> for the navigation to the next JSP/JSF page.
As far as I know the only difference between an common HTML form submission
and an XForms submission is, that XForms submits XML data, whereas HTML
submits key-value pairs/parameters. This basically is/should be no problem
for JSF.


> A rough guess is that a better solution would be to extend XForms with
> a mechanism to call up JSF event handlers. But then, you have to be
> careful with the handling of client-side HTML <form> elements, and
> make sure the JSF form and the Orbeon Forms form don't conflict. This
> would probably rquire changes in Orbeon Forms.

If I'm not wrong, this is basically what a custom JSF component like
<myjsf:model> does. It creates some XForms markup and extends it, by
internally registering some request/event handlers. And of course when
wrapping XForms markup in a custom JSF taglib, there still would be just one
form submission: the one that is generated by Orbeon Forms at the end of
request processing.


 >> The trick is seems to be to store the ID of the pressed button in
 >> the XForms instance data. During the decode process of the JSF
 >> framework, the instance data is parsed. So the JSF framework knows
 >> which button has been pressed and can call the registered action
 >> handler.

> That's understood. The problem is probably how to get the HTML form to
> make to to the JSF framework.

This is done by sending the form data to the same JSF page that rendered the
form.  So  if  the  page  that  renders  the  form  is available via the URL
/myapp/mypage.faces,  then  the  JSF framework usually creates a form within
that page like this:

<html:form action="/myapp/mypage.faces;session=xxxx" method="post">

So it sends the form data to "itself".


 >> Basically the problem is that the custom JSF components in the
 >> example renders XForms markup and I don't know why the Orbeon Forms
 >> filter does not convert these XForms markup into XHTML+JavaScript?
 >> This is why I can't check whether this way of JSF and XForms
 >> integration works with Orbeon Forms. :(

> That's another good one to figure out ;-)

That's currently the one that causes me headache...   :(


- bitbyter





--
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

On 5/24/07, BitByter <[hidden email]> wrote: And in your case, steps 1 to 3 are fine, but step 4 doesn't run. Is
this correct?

> Sometimes a day should have 48 hours or more...  :)

Not "sometimes"... a day should always have 48 hours! :)

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
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

Hello Alessandro,

Thursday, May 24, 2007, 2:28:17 PM, you wrote:

Exactly! This is where I'm currently stuck.

- bitbyter





--
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

On 5/24/07, BitByter <[hidden email]> wrote:
> Exactly! This is where I'm currently stuck.

OK. At least we have a good understanding of the problem :), but if
the filter is setup for the path you are requesting, I don't see why
it wouldn't be called. I am running out of ideas.

Alex
--
Orbeon Forms - Web 2.0 Forms for the Enterprise
http://www.orbeon.com/



--
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