XForms error: xforms:submit requires a submission attribute.

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

XForms error: xforms:submit requires a submission attribute.

Spenser Kao

Hi,

 

I have to revisit the issue again.

 

I know that at pages 9, 10 and 17 of OPS User Guide (pdf, ops 3.0.1) states that xforms:submit now requires a submission attribute.

But why the examples code of ATM, where xforms:submit is used to design the navigation between pages without declaring submission attribute (as no file, mailto or http protocol is needed), still work without such error?

 

Meanwhile, my trial to simulate the way ATM example codes use xforms:submit just kept receiving the error.

 

Can someone please give a clue?

 

Hope I am lucky this time to receive some response. Fingers crossed.

 

FYI, I am using OPS 3.0.1 under WinXP environment + JDK /JRE 1.5.

 

Regards,

 

Spenser

 



--
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: XForms error: xforms:submit requires a submission attribute.

Alexander Žaťko
The ATM example uses XForms classic that was neither as complete nor as clean implementation of the XForms spec as the newer XForms NG. The User Guide might also be out of date (not really sure about that as I have not read it for over a year). There exist also known bugs (check the bug tracking to make sure you have not run into something known before spending too much time flogging a dead horse):


Can you use the XForms NG for your project? You will get more help if you use that newer implementation of XForms.

A

On Sep 14, 2006, at 10:29 PM, Spenser Kao wrote:

Hi,

 

I have to revisit the issue again.

 

I know that at pages 9, 10 and 17 of OPS User Guide (pdf, ops 3.0.1) states that xforms:submit now requires a submission attribute.

But why the examples code of ATM, where xforms:submit is used to design the navigation between pages without declaring submission attribute (as no file, mailto or http protocol is needed), still work without such error?

 

Meanwhile, my trial to simulate the way ATM example codes use xforms:submit just kept receiving the error.

 

Can someone please give a clue?

 

Hope I am lucky this time to receive some response. Fingers crossed.

 

FYI, I am using OPS 3.0.1 under WinXP environment + JDK /JRE 1.5.

 

Regards,

 

Spenser

 


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



--
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: XForms error: xforms:submit requires a submission attribute.

Spenser Kao

Hi Alex,

 

So appreciate your reply.

 

Three more questions here:

 

1) Am I using the XForms NG for my project?

Here I quote OPS FAQ page [1] about the differing XForsm Classic from NG:  

If you are using OPS 2.8 or earlier, you are using XForms Classic. If you are using OPS 3.0 or If you are using OPS 2.8 or earlier, you are using XForms Classic. If you are using OPS 3.0 or later, then you may be using XForms Classic or XForms NG, but there is an easy way to tell: if a <page> entry in your page flow features an xforms attribute, then and only then that page is using XForms Classic. Otherwise, if the page view contains at least one XForms model under its xhtml:head element, then it is using XForms NG.

First, installation record indicates that I am using OPS 3.0.1, so I may be using either Classic or NG.

Secondly, all my working page-flow.xml files contain at least one XForms model under <xhtml:head>, but no xforms attribute, therefore it must be NG that I am using. Am my finding correct?

 

2) Is that link http://forge.objectweb.org/tracker/index.php?group_id=168&atid=350207 about bug ID 350207?

Clicking that link showed no bug with ID 350207, something I misunderstood?

 

3) Can you suggest a link where I can find example codes of using xforms:submit, under XForms NG, for navigating pages (not that action through file:, http: or mailto: protocol)?

 

Regards,

 

Spenser

 

[1] http://www.orbeon.com/ops/doc/home-faq

 


From: Alexander Zatko [mailto:[hidden email]]
Sent: Friday, 15 September 2006 1:00 PM
To: [hidden email]
Cc: 'Brad Heaton'; 'Lou Vaiano'; 'Mike Thanos'
Subject: Re: [ops-users] XForms error: xforms:submit requires a submission attribute.
Importance: High

 

The ATM example uses XForms classic that was neither as complete nor as clean implementation of the XForms spec as the newer XForms NG. The User Guide might also be out of date (not really sure about that as I have not read it for over a year). There exist also known bugs (check the bug tracking to make sure you have not run into something known before spending too much time flogging a dead horse):

 

 

Can you use the XForms NG for your project? You will get more help if you use that newer implementation of XForms.

 

A

 

On Sep 14, 2006, at 10:29 PM, Spenser Kao wrote:



Hi,

I have to revisit the issue again.

I know that at pages 9, 10 and 17 of OPS User Guide (pdf, ops 3.0.1) states that xforms:submit now requires a submission attribute.

But why the examples code of ATM, where xforms:submit is used to design the navigation between pages without declaring submission attribute (as no file, mailto or http protocol is needed), still work without such error?

Meanwhile, my trial to simulate the way ATM example codes use xforms:submit just kept receiving the error.

Can someone please give a clue?

Hope I am lucky this time to receive some response. Fingers crossed.

FYI, I am using OPS 3.0.1 under WinXP environment + JDK /JRE 1.5.

Regards,

Spenser

 

--

You receive this message as a subscriber of the [hidden email] mailing list.

To unsubscribe: [hidden email]

For general help: [hidden email]

ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

 



--
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: XForms error: xforms:submit requires a submission attribute.

Alexander Žaťko
Spenser,

#1 - Ryan Puddephatt answered this question today.

#2 - the particular bug ID argument that the URL for accessing the bug list contains was purely accidental - I had the bug list bookmarked by pointing to that defect. It might or might not have been relevant to the discussed issue. I thought I gave you a URL to the bug list - sorry for the confusion.

#3 - check http://www.orbeon.com/ops/ - all examples with names that show "XForms NG" rendered in orange text use XForms NG engine :-)

A.

On Sep 15, 2006, at 6:02 AM, Spenser Kao wrote:

Hi Alex,

 

So appreciate your reply.

 

Three more questions here:

 

1) Am I using the XForms NG for my project?

Here I quote OPS FAQ page [1] about the differing XForsm Classic from NG:  

If you are using OPS 2.8 or earlier, you are using XForms Classic. If you are using OPS 3.0 or If you are using OPS 2.8 or earlier, you are using XForms Classic. If you are using OPS 3.0 or later, then you may be using XForms Classic or XForms NG, but there is an easy way to tell: if a <page> entry in your page flow features an xforms attribute, then and only then that page is using XForms Classic. Otherwise, if the page view contains at least one XForms model under its xhtml:head element, then it is using XForms NG.

First, installation record indicates that I am using OPS 3.0.1, so I may be using either Classic or NG.

Secondly, all my working page-flow.xml files contain at least one XForms model under <xhtml:head>, but no xforms attribute, therefore it must be NG that I am using. Am my finding correct?

 

2) Is that link http://forge.objectweb.org/tracker/index.php?group_id=168&atid=350207 about bug ID 350207?

Clicking that link showed no bug with ID 350207, something I misunderstood?

 

3) Can you suggest a link where I can find example codes of using xforms:submit, under XForms NG, for navigating pages (not that action through file:, http: or mailto: protocol)?

 

Regards,

 

Spenser

 

[1] http://www.orbeon.com/ops/doc/home-faq

 


From: Alexander Zatko [[hidden email]]
Sent: Friday, 15 September 2006 1:00 PM
To: [hidden email]
Cc: 'Brad Heaton'; 'Lou Vaiano'; 'Mike Thanos'
Subject: Re: [ops-users] XForms error: xforms:submit requires a submission attribute.
Importance: High

 

The ATM example uses XForms classic that was neither as complete nor as clean implementation of the XForms spec as the newer XForms NG. The User Guide might also be out of date (not really sure about that as I have not read it for over a year). There exist also known bugs (check the bug tracking to make sure you have not run into something known before spending too much time flogging a dead horse):

 

 

Can you use the XForms NG for your project? You will get more help if you use that newer implementation of XForms.

 

A

 

On Sep 14, 2006, at 10:29 PM, Spenser Kao wrote:



Hi,

I have to revisit the issue again.

I know that at pages 9, 10 and 17 of OPS User Guide (pdf, ops 3.0.1) states that xforms:submit now requires a submission attribute.

But why the examples code of ATM, where xforms:submit is used to design the navigation between pages without declaring submission attribute (as no file, mailto or http protocol is needed), still work without such error?

Meanwhile, my trial to simulate the way ATM example codes use xforms:submit just kept receiving the error.

Can someone please give a clue?

Hope I am lucky this time to receive some response. Fingers crossed.

FYI, I am using OPS 3.0.1 under WinXP environment + JDK /JRE 1.5.

Regards,

Spenser

 

--

You receive this message as a subscriber of the [hidden email] mailing list.

To unsubscribe: [hidden email]

For general help: [hidden email]

ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

 


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



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