Matt, yes there will certainly be frequent new versions of Dojo to fix bugs, broaden browser compatibility, improve performance and security, etc. I think if Dojo maintains a decent reputation for maintaining backwards compatibility that developers will want their webapp to use the "server provided version" (which they may need to upgrade using Geronimo's standard deployment mechanisms). However, when a developer has hacked their Dojo library or just needs an extra boost of certainty about their runtime env they can certainly still include a private copy in their webapp instead of referencing the server copy.
To me the question of which approach a developer would want to take (private vs shared version) is analogous to deciding whether or not a deployment plan should include a version number in its gbean references (and none of the Geronimo configurations or assemblies do, AFAIK). Best wishes, Paul On 8/12/06, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
How about versioning of the Dojo libraries over time? I haven't played with the AJAX stuff really but I assume we'll be seeing new versions, etc. over time where different applications would be looking for different levels of the dojo libraries. So the goal would be use our "server provided version" and override it in your app if you need a newer one? Paul McMahan wrote: > Dojo is a popular open source AJAX library that's available under the > BSD and Academic Free licenses. The DayTrader folks use it in the web > UI they recently announced on the Geronimo dev list and Chris used it > in the nice LDAP UI he did for GERONIMO-1823. I would also like to > start introducing some use of it into the Geronimo admin console when > its appropriate to do so. > > The way that developers usually incorporate an AJAX library into their > applications is by making a copy of its static files (javascript, css, > gifs, etc) in their webapp and referencing them from their servlets > and JSPs. The obvious downside is that each application has a > separate copy of the AJAX library, increasing the server's overall > disk footprint (Dojo is ~3mb) and preventing the browser from using a > single copy of the library files from its cache. Another downside is > that the AJAX library can't be upgraded independently from the web > application. > > I think it would be great if Geronimo could provide a more AJAX > friendly development environment by helping solve these problems. One > idea is that Geronimo could include the Dojo library as a native, > standalone webapp with its AJAX library files laid out so that other > applications can point at from their HTML. Referencing it in > geronimo-web.xml would cause Geronimo to start it up and make its > files available at some predetermined context root, say /dojo. > Referencing it with a versionless moduleId would make sure the most > recent version is always used. So AJAX enabling your application in > Geronimo would be a simple as "add this line to your > geronimo-web.xml". > > Does this sound like a good idea? Any suggestions or concerns? > Perhaps this could be done as a plugin instead of a native module? > > Best wishes, > Paul > > >
