为什么Eclipse在尝试转换applet时会返回错误，而NetBeans却没有？

Question

Below, you see a Java Card program that acts as a 8 byte random number generator :

package randGen;

import javacard.framework.APDU;
import javacard.framework.Applet;
import javacard.framework.ISOException;
import javacard.framework.JCSystem;
import javacard.framework.Util;
import javacard.security.RandomData;

public class RandGen extends Applet {
    byte[] generatedArray;
    RandomData randData =   RandomData.getInstance(RandomData.ALG_SECURE_RANDOM);

    private RandGen() {
        generatedArray = JCSystem.makeTransientByteArray((short)8, JCSystem.CLEAR_ON_DESELECT);
    }

    public static void install(byte bArray[], short bOffset, byte bLength)
            throws ISOException {
        new RandGen().register();
    }

    public void process(APDU arg0) throws ISOException {
        byte[] byffer = arg0.getBuffer();
        byte[] generatedRandom = MyGenerator(arg0);
        Util.arrayCopyNonAtomic(generatedRandom, (short) 0, byffer, (short) 0,
                (short) generatedRandom.length);
        arg0.setOutgoingAndSend((short) 0, (short) generatedRandom.length);
    }

    public byte[] MyGenerator(APDU apdu) {
        randData.generateData(generatedArray, (short) 0, (short) 8);
        return generatedArray;
    }

}

This program converts to .cap file successfully in NetBeans IDE, but when I wanted to do the same operation with the Eclipse IDE, it returns the below error in respond of my request for conversion the applet :

error: randGen: empty package.

I added an image also : (As you see there is not error in the code, but the project directory marked with a red times mark as a sign of an error)

Update : I used Java Card 2.2.2 SDK and Eclipse-JCDE 0.2 plugin to convert my program to cap files in Eclipse.

Any idea?

Answer 1

Sometimes Eclipse fails to completely delete the .class files or .cap files on Windows machines, usually due to a program (eg McAfee or another virus scanner) locking files. In that case not all files will be deleted. In that case the right builders may not get triggered and you will get weird failures.

Those kind of errors are of course horrible to detect. Instead, if something fails uncontrollably, be sure to clean your build so Eclipse can retry. If you've changed code, first refresh, then clean (and possibly, refresh again). Anything to get the project state synced with the actual state on disk really.