To the guys that keep wanting me to dl debuggers, if you noticed, I said I put "debugger" in the javascript. That implies that I have a debugger. That it doesn't generate the required popup indicates a problem that the debugger will never find. I do appreciate you wanting to help, though. I would encourage you to continue.
Bear, it just differs in the location. We're using the Websphere Application Server at both the non-problem and the problematic locations. The main difference between them is that the new one is set up as a network server, whatever that means, and our current servers are not. I know very little about the servers.
What we use on our current deployments are:
http://devweb.com/ra/..., http://testweb.com/ra/..., and
http://prodweb.com/ra/... . The new site uses the fully qualified name plus the port. Shouldn't matter because I use the port when
testing on my localhost --
http://localhost:9443/ra/... (I've even used 127.0.0.1 successfully). At least, you'd think, huh?
I don't know. I take it that you've never heard of anything like this, either. I've been working with javascript for only two years, so I'm not as familiar with it as I would like. I'm trying a bunch of things, even pulling all the javascript right into the page -- that may be the only way this popup works. It's actually a forced dependent -- doesn't reload the
jsp when changed until the entire page is refreshed. Kind of sucks eggs, but I bet it will work greaat then. Shucks.
Well, thanks a lot, Bear. I appreciate the attempt.
[ January 16, 2007: Message edited by: Pat Flickner ]
Thanks.
