WebSeal and DWR

[Luca Vogna]

Hello,

I am using webseal to map my application URLs to domain wide URLs.

Ex:
https://mydomain.test.com:8080/GEN/dwr

is mapped to
https://mywebsealdomain.test.com/GENTEST/GEN/dwr

and I am accessing my domain using the second URL.

I experienced the infamous javascript "internal error" popup message. I thought it was something related with URL composition and I was right when I opened my dynamically generated javascript:

// Provide a default path to dwr.engine
if (dwr == null) var dwr = {};
if (dwr.engine == null) dwr.engine = {};
if (DWREngine == null) var DWREngine = dwr.engine;

if (PojoService == null) var PojoService = {};
PojoService._path = '/GEN/dwr';
PojoService.execute = function(p0, callback) {
  dwr.engine._execute(PojoService._path, 'PojoService', 'execute', p0, callback);
}

as you can see, the PojoService._path = '/GEN/dwr';   isn't generated after the mapping that I made on webseal, but it took the web context, the dwr servlet name mapping and store it inside the javascript file.

I am new to DWR technology and I would like to know whether there's is any well-known mechanism to bypass this problem, because I found nothing useful in the documentation, but of course I may be wrong.

Thank you a lot

[seadog00]

Hi,

I was having the exact same problem in my non-development server environments which are fronted by webseal, so I modified my javascript code on document load for each page that uses DWR to obtain and set the correct value for the _path attribute (based on the action value of the page's form).  After I did this, the calls started making it back to the app server, but I started receiving "Session Error" messages.  I tried first adding and setting the "allowScriptTagRemoting" parameter value to false, which did not work.  So, I finally disabled security by setting the "crossDomainSessionSecurity" parameter value to false, which works for now.  Of course, I want to enable security, so if anyone has found a solution to this issue, please post a reply.

Just to note, I had DWR working perfectly fine in two single-server development environments (one being my local machine and another being a remote server), so I feel certain the introduction of webseal into the picture is the root cause of the problem.

Thanks again for any help!

--Chuck

Luca Vogna wrote:

Hello,

I am using webseal to map my application URLs to domain wide URLs.

Ex:
https://mydomain.test.com:8080/GEN/dwr

is mapped to
https://mywebsealdomain.test.com/GENTEST/GEN/dwr

and I am accessing my domain using the second URL.

I experienced the infamous javascript "internal error" popup message. I
thought it was something related with URL composition and I was right when I
opened my dynamically generated javascript:

// Provide a default path to dwr.engine
if (dwr == null) var dwr = {};
if (dwr.engine == null) dwr.engine = {};
if (DWREngine == null) var DWREngine = dwr.engine;

if (PojoService == null) var PojoService = {};
PojoService._path = '/GEN/dwr';
PojoService.execute = function(p0, callback) {
  dwr.engine._execute(PojoService._path, 'PojoService', 'execute', p0,
callback);
}

as you can see, the PojoService._path = '/GEN/dwr';   isn't generated after
the mapping that I made on webseal, but it took the web context, the dwr
servlet name mapping and store it inside the javascript file.

I am new to DWR technology and I would like to know whether there's is any
well-known mechanism to bypass this problem, because I found nothing useful
in the documentation, but of course I may be wrong.

Thank you a lot