Enterprise Client Community

Hi there,

I have a scenario where I call a risc page which the server delivers correctly. Only the client side has problems running the JavaScript correctly. It doesn't find references which hints to JavaScript functions not being available:

ReferenceError: RISCConfirmExit is not defined
ReferenceError: RISCWindowMgr is not defined
ReferenceError: RISCPage is not defined

The client jar is available in the webapp on Tomcat. The problem is browser independent.

Under which circumstances can something like that happen?

Hi,

the client is a single page JavaScript application, so this is some bug there.

Could you please...

1. start the application with URL parameter "cclogactive=true" (e.g. http://localhost/xxx/start.tisc?cclogactive=true

2. Open the browser console by pressing F12 in the browser and then open the console-tab

3. Check the output there + send it over to us? (mail to info@CaptainCasa.com)

THANKS!

Björn

Hi,

thanks for answering. The output you see in my post is the client log output.

After further investigation another question came up: When I load a risc page which itself loads a number of stylesheets, scripts and images does it make sense to send a redirect for every reload of these resources? It seems to me it doesn't and even may break the rendering of the target page.

Problem solved. It's as described.
Reloading content into DOM of a RISC page must not make use of redirects.