> The problem is that the connection to the X display happens when the AWT
> native library is first loaded. It's a single connection that is used
> through the life of the JVM. As currently structured, the AWT won't let
> you associate different objects with different X connections. It would
> ta
allen petersen wrote:
>
> you know, it would probably make a whole lot more sense to integrate the jvm
> with something like gnome or kde rather than with the operating system itself.
> that way you skip the various xdisplay problems (since you'll necessarily have
> an x environment associated wi
you know, it would probably make a whole lot more sense to integrate the jvm
with something like gnome or kde rather than with the operating system itself.
that way you skip the various xdisplay problems (since you'll necessarily have
an x environment associated with your session) and you don'
Yavor Kolarov wrote:
>
> There are some additional problems.
>
> If we have a wrapper starting all programs it has to be able to:
> - open news windows and frames on a specific X terminal. ( User A running
> Java application on localhost:0.0 and user B on localhost:1.0)
> This raises the questio
