dev@woodstock.java.net

Issue 1333 Update

From: Jason Lee <jasondlee_at_sun.com>
Date: Wed, 17 Sep 2008 10:57:58 -0500

I've been poking at issue 1333 (https://woodstock.dev.java.net/issues/show_bug.cgi?id=1333
) and here's what I've seen/learned so far.

The code that adds onAvailableChange to the the addRemove component is
in woodstock4_3._html.addRemove._init. It also appears that all of
the components' JS files get mashed into webui*.js. In looking at our
page, we were including webui.js, which did not have anything related
to addRemove in it. I set webuiJsfx and webuiAll to true, and get
webui-jsfx-all.js included on the page, which finally has the
addRemove declaration. However, when I put a breakpoint in firebug on
the first line in woodstock4_3._html.addRemove._init, the breakpoint
is never tripped, which makes me think that the component isn't being
initialized correctly, but the fact that it does render seems to
contradict that.

One issue we've faced in the admin console was our broken JS. We
weren't using the defined WS APIs in certain areas, so the upgrade to
4.3 broke some of our code. Given the error I was seeing, I thought
I'd chase that rabbit a bit inside the WS code. My hope was that, for
some reason, the component was getting a reference to an incorrect DOM
element when trying to call availableOnChange, so I used Firebug to
look at every DOM element associated with the component. Of all the
divs, tables, spans, imgs, etc. not one had availableOnChange defined
on it, which lends credence to my assessment above, further muddying
things.

Is there somewhere more familiar with this component (and possibly how
the WS components are initialized on the client) who can help me walk
through this issue? We really need to get this resolved for GlassFish
ve Prelude.

Thanks!

Jason Lee - x31197
Senior Java Developer, Sun Microsystems
GlassFish Admin Console Team
Email: jasondlee_at_sun.com