[Jikesrvm-core] Jikes security model

[Thomas L R. <tl...@us...>]

Is Jikes' security model "J2SE-standard"? What I mean:

I am working to provide JUnit-based test automation for SWT GUIs

http://w3.opensource.ibm.com/projects/abbotforswt/

by wrapping Abbot

http://sourceforge.net/projects/abbot

which provides automation (i.e. programmatically puts events into the
native queue) for AWT/Swing UIs. The good news is, it works. However,
it uses java.awt.Robot as its event pump. j.a.Robot assumes the Sun
security model, and thus does things like

/* determine if the security policy allows Robot's to be created */
private void checkRobotAllowed() {
   synchronized(Robot.class) {
     SecurityManager security = System.getSecurityManager();
     AWTPermission createRobotPermission = null;
     if (security != null) {
       if (createRobotPermission == null) {
         createRobotPermission = new AWTPermission("createRobot");
       }
       security.checkPermission(createRobotPermission);
     }
   }
}

Concerns have been expressed regarding the portability to non-Sun JDKs
of automation solutions using java.awt.Robot. So I have a general
question and a specific one:

My understanding is that j.a.Robot and j.a.AwtPermission are part of
the J2SE spec; thus all compliant JDKs will have these classes and
those on which they rely. Is that correct?

Specifically, is Jikes thus compliant? Would someone likely experience
a problem using j.a.R or dependent classes on Jikes?

TIA, Tom Roche <tl...@us...>
WebSphere Studio Model2 Tooling, abbotforswt admin