Archives of the TeradataForum

Message Posted: Tue, 20 Aug 2002 @ 14:26:35 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hello all-

--- McBride, Michael wrote:

As a quick question, your previous mails indicated that there was a message alluding to the manifest of the jar being a problem, this could be an issue, as the manifest is (from my limited understanding) similar to an index of the classes contained in the jar. But, as your classes work outside of the jar, I can't really see that your jar was corrupted when you got it. If there is a way of doing a checksum of your class files against a fresh un-jar'd fileset, and see if your manifest is different in any way, I would look at that as one idea. I would also re-jar them myself and see if you get the same error. The initial error somewhat pointed to a classpath issue, but it was failing after it had found the jar, the possibilities seemed to be limited to

- the path in the jar being different from what you had to specify (from the doc)

- the jar file having some incompleteness somewhere

I'm still not sure if these will help, but it's where I would start to look for answers.

Thanks,

loadc

	<Prev	Next>		<<First	<Prev	Next>	Last>>