Hi Jay, from what I understand cross domain javascript security only
comes into play when the javascript and the html that references it
come from different domains (i.e. different hostnames and/or subnets).
Unless I'm mistaken I don't think what's been proposed in this thread
would be affected by cross domain security since the webapps and the
Dojo files would be hosted on the same server, albeit under different
contexts.

Thanks for offering to help test this out.  I'll send you a WAR file
containing the Dojo files in a separate email.  You should be able to
deploy the WAR into Geronimo, remove Dojo from your webapp, and then
point your webapp's html at "/dojo/dojo.js".

Best wishes,
Paul

On 8/14/06, Jay D. McHugh <[EMAIL PROTECTED]> wrote:
Hello all,

The application that I am currently developing under Geronimo is using
Dojo (mostly for it's asynchronous HTTP support).

Because it is a javascript library, there are limitations that come up
if you ever try to cross domains in your URLs.

Those limitations are basically that you cannot use javascript to access
a different domain that the one the javascript was called from (at least
that is how I currently understand it).  They did that to prevent
cross-site scripting abuse.

But, I do have everything that I need working right now.  So I would be
more that happy to do testing for pulling the Dojo library out of my war
files and referencing a single shared library (as long as you use
version 0.3.1 or higher - the current version).

Jay

Reply via email to