[ http://issues.apache.org/jira/browse/COCOON-1906?page=all ]

Lars Trieloff updated COCOON-1906:
----------------------------------

    Attachment: cocoon-forms-javascript-disambiguation.patch

Hi Vadim,

thank you for the hint. Using the attached patch, which will disambigue the 
method using the methodology described at 
http://www.mozilla.org/js/liveconnect/lc3_method_overloading.html I am able to 
run the modified samples in the way intended.

So the other patches are obsolete.

> [PATCH] simple-xml binding does not work with non file sources
> --------------------------------------------------------------
>
>                 Key: COCOON-1906
>                 URL: http://issues.apache.org/jira/browse/COCOON-1906
>             Project: Cocoon
>          Issue Type: Bug
>          Components: Blocks: Forms, * Cocoon Core
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Lars Trieloff
>         Attachments: cocoon-forms-javascript-disambiguation.patch, 
> cocoon-formsbinding-sample.patch, cocoon-formsbinding-sourceutil.patch
>
>
> The cocoon forms flowscript API comes with a helper method form.loadXML, that 
> retrieves data from an xml document. The current implementation however does 
> not work with documents that are referenced not as files, but as 
> SitemapSources, e.g. via the cocoon:/ or xmldb:// pseudo-protocol. In this 
> case the Rhino engine is unable to resolve the ambiguity between two method 
> signatures:
> org.mozilla.javascript.EvaluatorException: 
> "resource://org/apache/cocoon/forms/flow/javascript/Form.js", line 287: The 
> choice of Java constructor toSAX matching JavaScript argument types 
> (org.apache.cocoon.components.source.impl.SitemapSource,org.apache.cocoon.forms.util.XMLAdapter)
>  is ambiguous; candidate constructors are:
> void toSAX(org.apache.excalibur.xml.sax.XMLizable,org.xml.sax.ContentHandler)
> void toSAX(org.apache.excalibur.source.Source,org.xml.sax.ContentHandler)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to