February 23, 2007

Lotus Notes and Domino references

References/guides/tutorials:

Wikis:
Code/Libraries:
AdminP resources:

Notes.ini resources:
Education:
Product information:
Composite Applications:
Articles:
Interesting technotes:
Interesting redbooks:
Featured documents:
Notes/Domino Best Practices:
Out Of Office resources:
Test infrastructure documents:
Blogs:
Tips & Tricks:
Podcasts:
Java in Notes:
Unsorted:


Technorati tags:
, , , ,


Posted by Niklas Waller at 2:10 PM 0 comments

February 01, 2007

AJAX problems in Firefox

I have been writing an AJAX-application that calls one or several SOAP web Services and presents the result on a single web page in different div tags. Due to some css-functionality a really nice look and feel can be accomplished similar to a portal site with many different portlets. In this case each porlet would consist of a div tag. This is all done in Lotus Notes/Domino but can be moved to any system (!?). I will present it in more detail here later on but for now I'd like to share a limitation that bothers me with Firefox or Mozilla browsers in general, maybe others as well.

If you're using AJAX where the requesting page and the Web Service resides on the same domain it works in any browser since the XMLHttpRequest object is univeral to any browser. However if the requesting page and the Web Service resides on different domains you'll find that it will not work in Firefox. An error will be raised looking like this:
Uncaught exception: Permission denied to call method XMLHttpRequest.open

The error is raised because of security concerns. Appearantely most web browsers (IE excluded) is restricted by default to interact only with resources and services hosted by the same domain. The reason is to keep potentially malicous code from accessing information it shouldn't have access to.

However, as I see it there is an equal need to communicate with Web Services that is not located on the same domain as Web Services located on the same domain. There are two ways to accomplish this:

  1. Digitally sign the Javascripts. Read more about this on Mozilla.org. I started digging into this but got really tired and sick of it since it is required by me to:
    1. Download a sign tool and learn how to use that. The sign tool creates a jar-file when executed to point to.
    2. Add specific exception handling functions
    3. Get a certificate and pay for it
    4. Whenever I change my javascript I have to resign it to create a new jar-file to use.
  2. Use a proxy. I don't know how this is supposed to work but the point is that it will work if all requests from the XMLHttpRequest object is passed through a proxy resource located on the same domain as the requesting page
Anyway, I guess it has to be done if you want your applications to work on anything else than Internet Explorer 6, which is what I have tested this on together with Firefox 2.0.

My resources recommendations are:


Technorati tags:
, , , , , ,


Posted by Niklas Waller at 10:19 AM 0 comments

Subscribe to: Posts (Atom)