-
Enhancement
-
Resolution: Unresolved
-
P4
-
None
-
1.3.1, 1.4.0
-
Fix Understood
-
generic, x86
-
generic, linux
Name: gm110360 Date: 04/18/2002
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
FULL OPERATING SYSTEM VERSION :
Linux, Solaris, and Windows
A DESCRIPTION OF THE PROBLEM :
I submitted a bug against being able to set and get the
DISPLAY information about the X11 server.
Any AWT initialization automatically tries to connect to an
X11 server. This needs to have the DISPLAY environment
variable set.
My request is for a way to tell the AWT which X11 server to
connect to, with out using the DISPLAY environment variable.
We need a way to direct the AWT programatically, with a
setDisplay( host:screen ) call on the AWT toolkit, graphics
environment, or something.
I have not heard any information on a work around besides
setting the DISPLAY environment variable manually before
running my java application. This work around is not
enough.This is a major bug in application development.
Thank you.
This bug can be reproduced always.
(Review ID: 145580)
======================================================================
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
FULL OPERATING SYSTEM VERSION :
Linux, Solaris, and Windows
A DESCRIPTION OF THE PROBLEM :
I submitted a bug against being able to set and get the
DISPLAY information about the X11 server.
Any AWT initialization automatically tries to connect to an
X11 server. This needs to have the DISPLAY environment
variable set.
My request is for a way to tell the AWT which X11 server to
connect to, with out using the DISPLAY environment variable.
We need a way to direct the AWT programatically, with a
setDisplay( host:screen ) call on the AWT toolkit, graphics
environment, or something.
I have not heard any information on a work around besides
setting the DISPLAY environment variable manually before
running my java application. This work around is not
enough.This is a major bug in application development.
Thank you.
This bug can be reproduced always.
(Review ID: 145580)
======================================================================
- duplicates
-
JDK-4513617 RFE: Be able to set and get the DISPLAY Variable Dynamically
-
- Closed
-