This content has been marked as final. Show 3 replies
Sorry, no, not at all. (By the way, it was earlier the case, but I discovered that a class that I jar'ed myself was not transformed with the "0" switch--hence, jar delivered a zip-compressed version). However, at the time being this is legacy software, from Cardcontact in Germany; I inspected the guilty class and one another by first extracting them with jar xf, then examining them in hexa notation. Both begin with 0xCAFEBABE. This is really a huge problem to me, because no auxiliary explanation is available. Can it be a side effect (e g CLASSPATH, PATH etc.?) CLASSPATH has both jar files in it. Otherwise the Applet technique would work A1.