Migrating from 3.6.0 to 3.7.0beta1 - issues with submission on xforms-ready

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

Migrating from 3.6.0 to 3.7.0beta1 - issues with submission on xforms-ready

fl.schmitt(ops-users)
Hi,

i'm trying to migrate my xforms app including some javascript and css
resources to 3.7.0beta1. Authentication works (non-xforms), but the
first xforms page fails to load - it seems that a submission that's
issued on  ev:event="xforms-ready" fails to execute:

<xforms:send ev:event="xforms-ready" submission="ldap-subm" />

If i comment that line out, the pages loads completely (but without some
css styles - see below).

Firebug says:

----------
element has no properties
http://localhost:8080/dokdb-3.7.0/ops/javascript/xforms.js
Line 294

hasClass(null, "xforms-trigger-appearance-modal")
executeNextRequest(true)
(no name)()
-----------

with the word 'null' (first parameter of hasClass) selected.

Lines 290 of xforms.js are looking as follows:

290 /**
291 * Optimized version of YAHOO.util.Dom.hasClass(element, className).
292 */
293 hasClass: function(element, className) {
294 if (!element.orbeonClasses) {
295 element.orbeonClasses = {};
296 var classes = element.className.split(" ");
297 for (var i = 0; i < classes.length; i++)
298 element.orbeonClasses[classes[i]] = true;
299 }
300 return element.orbeonClasses[className] == true;
301 },




Another problem: there are no css styles applied to the html headings
(h1 and so on), also the gridtable class for tables seems to have no
effect. Maybe a css file is missing or cannot be found? How to implement
own css files besides the orbeon ones? I've put mine into the /config
dir and added some xhtml:link elements into theme-plain.xsl and changing
the theme in properties.xml).


Thanks in advance!


florian



--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Migrating from 3.6.0 to 3.7.0beta1 - issues with submission on xforms-ready

Erik Bruchez
Administrator
Florian,

> Firebug says:
>
> ----------
> element has no properties
> http://localhost:8080/dokdb-3.7.0/ops/javascript/xforms.js
> Line 294
>
> hasClass(null, "xforms-trigger-appearance-modal")
> executeNextRequest(true)
> (no name)()
Any way this can be reproduced in a simple example?

> Another problem: there are no css styles applied to the html headings
> (h1 and so on), also the gridtable class for tables seems to have no
> effect. Maybe a css file is missing or cannot be found? How to  
> implement
> own css files besides the orbeon ones? I've put mine into the /config
> dir and added some xhtml:link elements into theme-plain.xsl and  
> changing
> the theme in properties.xml).

I assume you were relying on orbeon.css? What CSS files are currently  
included (do a view source in the browser)?

orbeon.css is just CSS for the Orbeon examples, it really shouldn't be  
used for other purposes ;-)

You can add your own link to CSS the usual way: by adding an html/head/
link. You can do this in every page, or do this in a theme stylesheet.  
You can now set the theme stylesheet with a property. By default it is  
as follows:

   <property as="xs:anyURI" name="oxf.epilogue.theme" value="oxf:/
config/theme-examples.xsl"/>

I would start with theme-plain.xsl, rename that to theme-
florian.xsl ;-), and then change the property in properties.xml.

Best,

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Migrating from 3.6.0 to 3.7.0beta1 - issues with submission on xforms-ready - SOLVED

fl.schmitt(ops-users)
Erik,

thank you for your reply and your help!

> Any way this can be reproduced in a simple example?

Trying to build such a example led me to the solution - the cause wasn't
the submission, it was a javascript call that depended on the output of
that submission. They were both triggered by xforms-ready, now the
javascript is triggered by xforms-submit-done, and everything works. The
strange thing is that even the CSS files are applied correctly now.

florian




--
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
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: Migrating from 3.6.0 to 3.7.0beta1 - issues with submission on xforms-ready - SOLVED

Erik Bruchez
Administrator
> Trying to build such a example led me to the solution - the cause  
> wasn't
> the submission, it was a javascript call that depended on the output  
> of
> that submission. They were both triggered by xforms-ready, now the
> javascript is triggered by xforms-submit-done, and everything works.  
> The
> strange thing is that even the CSS files are applied correctly now.

Phew ;-) Thanks for letting us know.

-Erik

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
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
OW2 mailing lists service home page: http://www.ow2.org/wws