JCardEngine is designed as a rapid development and testing aid for JavaCard applets, providing lightweight ephemeral JavaCard environments to run applet code on a traditional JVM and exchange APDU-s with it. It does this by simulating (mocking) the JavaCard framework packages (javacard*.framework.*) and system classes (JCSystem, GPSystem etc) and taking care of applet initialization and registration via your Applet.install() method. Cryptography is provided via Bouncy Castle. See Java Code Tutorial, Beginner.

It also comes as a command line utility jcard.jar to quickly fire up existing applet .cap files (that include Java .class files, do not use strip="true" with ant-javacard) and expose them via PC/SC adapter(s) to existing applications. See Command Line Tutorial, Beginner.

• seamless use from command line wiht jcard
• supports Global Platform with SCP03 secure channel
• programmatic components for PC/SC adapters
• simulator state introspection (JavaCard, GlobalPlatform)

Notes:

• WIP stands for Work In Progress
• https://forums.oracle.com/ords/apexds/post/jcdk24-1-amservice-generating-applet-code-coverage-using-c-9778

Issues with jcardsim and focus of the fork is split as follows:

• "core" and platform correctness
  • JC API revision conformance (transient keys, OneShot etc)
  • internal structures and interfaces (not visible to users)
  • build scaffolding (Maven, ASM, GHA, repo etc)
  • threading assumptions
• algorithm completeness and correction
  • PACE_GM, bugs etc
• interfacing and DX
  • virtual readers (javax.smartcardio, VSmartCard/BixVReader, Oracle PC/SC)
  • explicit composition of card (applets) vs indirect properties + instantiation
  • command line tool (not unlike GlobalPlatformPro)
  • interfacing to Oracle Simulator from same framework
• new features
  • GPSystem support via GlobalPlatformPro