[
https://issues.apache.org/jira/browse/XAP-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494895
]
Rob Gagne commented on XAP-219:
-------------------------------
MCOs allow you to set class and src.
Plugins now will read from the directory that the plugin is loaded from.
> We need to make Xap.require() more configurable, or at least give users a
> default directory for unrecognised prefices.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: XAP-219
> URL: https://issues.apache.org/jira/browse/XAP-219
> Project: XAP
> Issue Type: Improvement
> Components: MCOs, Widgets: Other
> Reporter: Turyn, Michael
>
> Currently, Xap.require() can only locate JS constructors with the prefices
> "xap.", "dojo.", and "google.". This makes it more difficult for users to
> bring in their own classes, most significantly in an MCO without a defined
> path to a source file. This also has implications for adding user-defined
> bridges and widgets.
> At the very least, we should configure XAP out-of-the-box with a an
> additional directory known to Xap.require(), so that a user who creates a
> file in (say)
> org/apache/format/YenFormatter.js
> will be able to use it using a simple MCO:
> <mco:mco class="org.apache.format.YenFormatter"
> id="yenFormatter"/>
> ---that is, XAP_ROOT/usr/ is a default directory for unrecognized prefices.
> Alternately, we should let Xap.require() know about additional prefix
> mappings using the configuration file. This is probably a better solution
> overall, can be wizardable,....
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
