[
https://issues.apache.org/jira/browse/COCOON-2062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510972
]
Alexander Klimetschek commented on COCOON-2062:
-----------------------------------------------
Well, it's simple: add
dojo.require("dojo.ns")
at the top (just below the dojo.provide statement) of these two files:
blocks/cocoon-ajax/cocoon-ajax-impl/src/main/resources/org/apache/cocoon/ajax/resources/manifest.js
blocks/cocoon-forms/cocoon-forms-impl/src/main/resources/org/apache/cocoon/forms/resources/manifest.js
> forms/ajax manifest.js miss include dojo.require("dojo.ns")
> -----------------------------------------------------------
>
> Key: COCOON-2062
> URL: https://issues.apache.org/jira/browse/COCOON-2062
> Project: Cocoon
> Issue Type: Bug
> Components: Blocks: Ajax, Blocks: Forms
> Affects Versions: 2.1.11-dev (Current SVN), 2.2-dev (Current SVN)
> Reporter: Alexander Klimetschek
> Assignee: Grzegorz Kossakowski
>
> cocoon-ajax-impl and cocoon-forms-impl are missing a dojo.require("dojo.ns")
> statement at the beginning because they access dojo.registerNamespace() which
> comes from that package. (No patch for this, since it's a one-liner)
> Sidenote: A workaround by manually adding this require in a script or other
> js file before manifest.js are accessed does noes work when you have
> djConfig.debugAtAllCosts enabled, since then dojo parses the js files for
> dojo.require() with a regexp (to avoid eval and adding all js files as script
> elements to the browser so that they appear correctly in your favourite
> javascript debugger). A missing require in that file will get the dependency
> order wrong.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
