You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Don Brown (JIRA)" <ji...@apache.org> on 2006/12/01 07:47:57 UTC
[jira] Updated: (WW-1477) Dojo Integration
[ http://issues.apache.org/struts/browse/WW-1477?page=all ]
Don Brown updated WW-1477:
--------------------------
Fix Version/s: Future
(was: 2.0.2)
Affects Version/s: 2.0.1
(was: Future)
Agreed, it would be nice...have a patch in mind? :) BTW, 2.0.2 will feature Dojo 0.4 so it should be less of an immediate issue
> Dojo Integration
> ----------------
>
> Key: WW-1477
> URL: http://issues.apache.org/struts/browse/WW-1477
> Project: Struts 2
> Issue Type: Improvement
> Components: Misc
> Affects Versions: 2.0.1
> Reporter: Mike B
> Priority: Minor
> Fix For: Future
>
>
> We are using Dojo outside of the WW Ajax theme and would also like to use some of the WW Ajax components. Currently, It is an all or nothing proposition. I can either choose to use the WW Ajax theme or Dojo independently, but not both.
> Clearly, having multiple references to dojo.js is a problem. Is it possible for WW to integrate Dojo in a more decoupled manor so that users who would like to keep up with the latest Dojo releases and use new Dojo components are not in a situation where it conflicts with internal WW tags?
> Maybe some configurations settings to specify where the Dojo base packages exist outside of the ww jar... ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira