chakaal
asked on
Mac fails to run Java app that works on PC
I am running a beta test on a Java application, it's on private servers so I can't point you there. I have a grab from the console log on a MAC running OS X 10.4.11 - JRE 1.5.0_16 - this app fails on the mac, but not on a PC or on a mac running JRE 1.5.0_13. I cannot swear there are no other differences between the two machines.
The system complains that it cannot parse the file helpset.hs, also there is a complaint about a malformed URL "map.jhm." Yes, the period is included in the error output.
No, I have No Business trying to figure this out myself, I am completely out of my element.
I have attached the console log in a .jpg - it doesn't seem to want to let me get the text from it.
It is not a complete snap, I am hoping someone can point me in the right direction or give me a clue for my developer. I've tried three or four of his solutions, none have worked.
Thanks,
M
image.jpg
The system complains that it cannot parse the file helpset.hs, also there is a complaint about a malformed URL "map.jhm." Yes, the period is included in the error output.
No, I have No Business trying to figure this out myself, I am completely out of my element.
I have attached the console log in a .jpg - it doesn't seem to want to let me get the text from it.
It is not a complete snap, I am hoping someone can point me in the right direction or give me a clue for my developer. I've tried three or four of his solutions, none have worked.
Thanks,
M
image.jpg
DJDecay
Are you using an obfuscator, or any assemblies are obfuscated?
ASKER
I have found/heard that this is a known Java bug, and the best I can hope for is a quick solution from them, or an easier work-around than the ones that have so far turned up. The bug prevents URLs from being retrieved from a JAR which is why the errors fall out as they do. I'm told it is a known, high-priority bug, but that doesn't tell me whether a fix will be fast or not.
I guess my search is now for a workaround my developer can put in place pretty easily, since he is unfortunately also rather new to Java. Failing that I may just have to deal with a broken application until there's a bug fix.
--M
I guess my search is now for a workaround my developer can put in place pretty easily, since he is unfortunately also rather new to Java. Failing that I may just have to deal with a broken application until there's a bug fix.
--M
Could you try uncompress the JARs into .java assemblies. Repoint CLASS_PATHS to assembly directories? It should be a quick workaround if you're in a pinch
.
.
ASKER
I'll run it up the flagpole and see if he salutes it...
M
M
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.