"Patrick J. McNerthney" wrote :
> > EXCELLENT, Thanks it solves the problem....
> >
> > Would you mind to explain me what was going wrong with the manifest file
> > ? Indeed it's a third party library, so I had to extract and rejar with
> > the M option. For the moment it's OK, but I'm afraid that other people
> > will fall in the same trap.
> I really don't know what the problem is, just the fix...my guess is that
> Sun pushed some of the jar handling into native code in 1.3 and
> introduced a bug. I haven't yet bothered to download the 1.3 source
> release to figure this one out.
> > So how can we avoid this ? Should we tell Sun about it ?
> You certainly could, I would first search their bug database to see if
> it is a known problem.
> Something I never checked out is if jar'ing with manifest generation
> under the 1.3 jar utility fixes the problem. I know the 3rd party
> library I had to do this with was originally jar'ed with a version prior
> to 1.3.
Well I did this and it make no difference... the only working option is
removing the manifest file. Just curious : how did you find out that ?
Thanks,
Sebastien
> Pat McNerthney
> Icicle Software, Inc.
