Hi,
I've been trying out the 3.9 RC 1 release with a reasonable amount of success until I've tried to use the XBL map component. Has anybody used this OK? Any ideas to help track this down gratefully received - see below for some diagnosis. Thanks, Ian It's part of a long complex form but I've narrowed the problem down to the following:(i.e. if all of this is removed then the form loads) <div> <xforms:select1 ref="country"> <xforms:label class="fixed-width">Country</xforms:label> <xforms:item> <xforms:label>please select</xforms:label> <xforms:value /> </xforms:item> <xforms:itemset nodeset="instance('ins-country-items')/country"> <xforms:label ref="label" /> <xforms:value ref="value" /> </xforms:itemset> <xforms:alert>Selecting a Country initialises the map </xforms:alert> <!-- <xxforms:show ev:event="xforms-select" dialog="dia-map"/> --> </xforms:select1> </div> <div> <xforms:input ref="latitude"> <xforms:label class="fixed-width">Latitude</xforms:label> <xforms:alert> <xforms:output value="concat('Enter a coordinate value between -180 and 180 for the ', name(), ' field ')" /> </xforms:alert> </xforms:input> </div> <div> <xforms:input ref="longitude"> <xforms:label class="fixed-width">Longitude</xforms:label> <xforms:alert> <xforms:output value="concat('Enter a coordinate value between -180 and 180 for the ', name(), ' field ')" /> </xforms:alert> </xforms:input> </div> <div class="mapPicker"> <p> <b>Drag the pointer to populate the Latitude and Longitude fields</b> </p> <fr:map address-ref="lookupAddress" longitude-ref="longitude" latitude-ref="latitude" style="width: 500px; height: 300px"> </fr:map> </div> What I'm seeing in the logs is a stack overflow: 2011-05-16 10:54:43,655 ERROR org.orbeon.oxf.processor.transformer.xslt.XSLTTransformer - Error at line 81 of oxf:/ops/utils/formatting/xml-formatting.xsl: Too many nested apply-templates calls. The stylesheet may be looping. 2011-05-16 10:54:43,659 WARN org.orbeon.oxf.xforms.processor.XFormsServer - exception while evaluating XPath expression {throwable: "org.orbeon.oxf.common.OXFException: line 81 of oxf:/ops/utils/formatting/xml-formatting.xsl (executing XSLT transformation): Too many nested apply-templates calls. The stylesheet may be looping. Too many nested apply-templates calls. The stylesheet may be looping. Lots of loops as follows: at org.orbeon.oxf.xforms.XFormsModel.rebuildRecalculateRevalidateIfNeeded(XFormsModel.java:1075) at org.orbeon.oxf.xforms.xbl.XBLContainer.rebuildRecalculateRevalidateIfNeeded(XBLContainer.java:725) at org.orbeon.oxf.xforms.xbl.XBLContainer.rebuildRecalculateRevalidateIfNeeded(XBLContainer.java:735) at org.orbeon.oxf.xforms.xbl.XBLContainer.synchronizeAndRefresh(XBLContainer.java:698) at org.orbeon.oxf.xforms.xbl.XBLContainer.endOutermostActionHandler(XBLContainer.java:671) -- 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 |
Administrator
|
Hi Ian,
Until a couple of weeks ago, xml-formatting.xsl was used by the XForms inspector, to show a nicely formatted version of the XML in the web page. Could you try turning off the XForms inspector, to see if you still get this error? 1. If it is indeed due to the inspector, maybe by now you don't care about it anymore, since you most likely only use it during development. 2. But if you would like the inspector to run properly, you can upgrade to a nightly build, which doesn't use server-side XSLT for formatting. 3. Finally, if the issue isn't caused by the inspector, could you put this together in an single file XForms that we can run in the XForms sandbox to reproduce this? Alex
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Hi Alex,
Removing the inspector changed the error message but upgrading to the release fixed it completely. Thanks, Ian On 19:59, Alessandro Vernet wrote: > Hi Ian, > > Until a couple of weeks ago, xml-formatting.xsl was used by the XForms > inspector, to show a nicely formatted version of the XML in the web page. > Could you try turning off the XForms inspector, to see if you still get this > error? > > 1. If it is indeed due to the inspector, maybe by now you don't care about > it anymore, since you most likely only use it during development. > 2. But if you would like the inspector to run properly, you can upgrade to a > nightly build, which doesn't use server-side XSLT for formatting. > 3. Finally, if the issue isn't caused by the inspector, could you put this > together in an single file XForms that we can run in the XForms sandbox to > reproduce this? > > Alex > > -- > View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/3-9-RC-1-and-XBL-maps-component-tp3526001p3531774.html > Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.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 |
Administrator
|
Ian,
Excellent, thank you for checking and confirming this one. Alex
--
Follow Orbeon on Twitter: @orbeon Follow me on Twitter: @avernet |
Free forum by Nabble | Edit this page |