views:

232

answers:

2

For a J2EE bean I am reusing code that was developed for a java swing application. JOptionPane.showMessageDialog() is unfortunately commonly used. Most occurences luckily in code sections that are not reused by the J2EE application, but in some cases lower levels of the code has instances of JOptionPane.showMessageDialog(). Obviously this it results in dialog boxes popping up on the server, which is what I want to avoid.

As a first step I'd like to somehow assure that no dialog boxes will ever occur on the server.

Someone suggested peeking in some event or paint queue (I do not recall which one): That would be:

// old code: JOptionPane.showMessageDialog(msg);
if ( someEventQueue.size() == 0 ) // <== consider this pseudo-code
  Log.log(msg); // I am running on a server. Tell the log.
else
  JOptionPane.showMessageDialog(msg); // I have a user made of meat. Tell him!

I never really got that working. What would you do?

+5  A: 

Make sure the server is started with

java -Djava.awt.headless=true

Most servers should be started that way by default. Then you can check:

GraphicsEnvironment ge = 
GraphicsEnvironment.getLocalGraphicsEnvironment(); 
boolean headless_check = ge.isHeadless();

More details on headless available here:

Brian
Or any custom system parameter, for example -Dnodialog=true .
kd304
Good Point. There is a plethora of System properties that would be unique to each environment. For Oracle OC4J application Server: System.getProperty("oracle.oc4j.instancename");
Brian
Its not about system dependant properties. You could use anything you want: -Dthis_is_a_param_for_no_dialog=true
kd304
The great thing about using the JVM option -Djava.awt.headless=true is that HeadlessException will be thrown each time JOptionPane.showMessageDialog(msg) is executed - and so on.
fredarin
A: 

How about checking for headless

if ( System.getProperty( "java.awt.headless" ) != null &&
   System.getProperty( "java.awt.headless" ) == true ) {
  // you shoud not use AWT/Swing 
}
Clint