RE: Another opinion on InfoCenter

Ugh.  Are you talking about the netscape.javascript package???  If
that's the case, I can see why you might have problems.  I dropped that
concept a long time ago.  If I want sophisticated JavaScript
interaction, I simply code the JavaScript to be configurable at runtime
and then generate a simple SCRIPT tag in my HTML to set any runtime
variables required.  I couldn't imagine trying to fight through the
arcanities of the JSObject interface.

I assume you're doing this in order to dynamically build the navigation
device by communicating with the host, and/or to allow interactivity
between the navigation pane and the content pane.  I'm sorry you've had
such problems, and I wish I could help.  All I can do is empathize with
your pain.

Joe

> From: Darel Benysh
> 
> Hi Joe, at a high level, the function we relied on to handle
interaction
> between the Java Applet and the JavaScript in the content was
defective.
> This problem manifest itself in different ways in different  browser
> application / JRE / OS environment configurations.  The manifestations
in
> our InfoCenter application ranged widely.  At one end, the system
simply
> did not execute the functions provided by the java->javascript
> interaction.
> In this case, users might not even notice that something wasn't
happening
> as designed.  At the other end, the problems were more severe and the
only
> way to regain control of the system was to manually kill the browser
> process.  There were also a number of variations in between.