Problem:

• Product Name: Borland Enterprise Server
• Product Version: 6.5
• Product Component: Signed JAR files
• Platform/OS Version: All 

Client programs are often distributed through Java Web Start, the JAR files must be signed in order for them to be accepted by the client machine. Some JAR files (asrt.jar, jds.jar,...) cannot be signed because the files fail a CRC check.

Resolution:

The reason the CRC check fails is because some of the executables are stamped with the version numbers after they are originally archived. The stamping technology modifies the contents of the archives but not the CRC. To sign a jar, current process is to do the unjar followed by jar, which works fine and this has been consistent issue from the older versions of BES AppServer. Hence, Change Request # 5839 has been filed as defect.

Subsequently, the bug fix is included in the base release of Borland Application Server 6.6