Created attachment 104761 [details]
Sun's sample organised as 2 NetBeans IDE projects.

Hi, 

I am trying to get the Sharable interface working across two applet packages.
I came across several problems in my own project, and decided to compile Sun's JavaPurse example to figure out what i was doing wrong:

Javacard_3_0_2_Classic/samples/reference_apps/PurseWithLoyalty/*

I created a first netbeans project "JavaLoyalty" - > Java Card 3 -> Classic -> Library
copied in the JavaCard_3_0_3 sample src code.
I compiled and got the following error message generated by the packager

"[Error] Only one package is allowed in a classic applet or classic library?"
--> I don't understand why the SUN/Oracle example applet does not compile? 

I created a second netbeans project "JavaPurse" - > Java Card 3 -> Classic -> Applet
copied in the JavaCard_3_0_3 sample src code.
In project properties, dependencies, added a library, project type, "Java Library", Deploy to Card strategy
In project properties, Applets, click JavaPurse, set instance to 0201

Assuming you just have one package in an applet then the next problem is that Sharable Interface handling doesn't work.  That is, the Packager does not know where to find the SIO.exp files from the classic library. I have tried many things to help the packager find the SIO.exp files, including toggling flags and manyally copying the SIO.exp to various locations, and can't make it work. 

I could not test this sample code in 6.9.x or 7.0.0 beta because of the following bug
http://netbeans.org/bugzilla/show_bug.cgi?id=189912 

I have included my basic setup for those 2 projects so the problem can be reconstructed quickly.

---
Please. Can a technician supporting NetBeans go through, compile all the java card sample code provided by Sun, and make sure it works in the IDE.  

Then, after performing this regression testing, publish those samples as NetBeans projects so we don't have to go through the learning curve to figure out how to setup the NetBeans IDE properly by brute-force testing all combinations.

I think the NetBeans Java Card support looks very promising, but it is extremely hard to use at this point in it's development cycle.