Home.... | log in.... | Pub my question! | Sign-up....
Java-index >> Desktop >> Deploying

Pack200 problems when server is Java6 and clients still Java5

I suddenly get errors like this:

"Corrupted pack file: magic/ver = CAFED00D/160.1 should be CAFED00D/150.7"

And only on certain jar files, not all, mostly on special resource jar files, But i dont know that (what they are) because it is a plugin structure where jnlp are generated for an then the jars files are asked for which are then on the fly packed if they wheren't packed already.

But if the server is java 6 and a client (that i can't control) is still java 5 then i get that error. How can i force the packer that it needs to make java5 compatible packs? Currently it is just not usable!

Is only the real solution to completely turn of the pack feature?

[696 byte] By [jocoa] at [2007-11-26 13:55:06]
«« WBEM is reality?
»» Discovering the types
# 1

ok i fixed it now like this:

if(usePack)

{

String serverJavaVersion = System.getProperty("java.specification.version");

String clientJavaVersion = request.getHeader("ua-java-version");

usePack = !(clientJavaVersion != null && serverJavaVersion != null && serverJavaVersion.indexOf("1.6") >= 0 && clientJavaVersion.indexOf("1.5") >= 0);

}

so that when the server is java 6 and the client is java 5 then pack will not be used. If anybody has a better idea to forge the packer into a better mode then i still would like to know that.

jocoa at 2007-7-8 1:33:58 > top of Java-index,Desktop,Deploying...
Desktop
Deploying

Desktop New Topic

Desktop Hot Topic

Desktop

All Classified