hello Casey,
On Tuesday 21 November 2006 08:35, Casey Marshall wrote:
> ...
> This patch fixes an issue with JarEntry objects that are created
> before the entry is verified: we used to bind the certificates to a
> JarEntry at creation time, so if the entry has not been verified yet,
> the certifi
On Nov 25, 2006, at 3:59 PM, Raif S. Naffah wrote:
hello Casey,
On Tuesday 21 November 2006 08:35, Casey Marshall wrote:
...
This patch fixes an issue with JarEntry objects that are created
before the entry is verified: we used to bind the certificates to a
JarEntry at creation time, so if the
On Sunday 26 November 2006 19:58, Casey Marshall wrote:
> On Nov 25, 2006, at 3:59 PM, Raif S. Naffah wrote:
> > On Tuesday 21 November 2006 08:35, Casey Marshall wrote:
> >> ...
> >> This patch fixes an issue with JarEntry objects that are created
> >> before the entry is verified...
> >
> > ...be
On Nov 27, 2006, at 12:08 AM, Raif S. Naffah wrote:
On Sunday 26 November 2006 19:58, Casey Marshall wrote:
On Nov 25, 2006, at 3:59 PM, Raif S. Naffah wrote:
On Tuesday 21 November 2006 08:35, Casey Marshall wrote:
...
This patch fixes an issue with JarEntry objects that are created
before t
On Nov 27, 2006, at 10:52 AM, Casey Marshall wrote:
On Nov 27, 2006, at 12:08 AM, Raif S. Naffah wrote:
any reason why you didn't address the synchronization issue in
JarEntry#getCertificates()?
I wasn't sure if it was needed.
It is needed, and JarFile explains that you need to lock on the