Jason T. Greene wrote:
Ales Justin wrote:
>> I finally have the cause:
>>
>> Deploy
>> ------
>> 1. Structure scanning creates tempX for the nested war
>> (ZipEntryContext-A)
>>
>> 2. During deployment JEEDeployedObject calls getResource, which opens
>> a vfs URL
>>
>> 3. The vfs registry cache lookup fails because ZipEntryContext-A is a
>> nested resource, thus the original deployment is rescanned.
>>
>> 4. ZipEntryContext-B is created in the same file context as A (the
>> deploy dir), therefore *tempX is reused* (see initEntries:539)
>
> Why exactly is ZEC-B created?
> It should be only one, as that's the point of having a cache.
It looks like nested zip entries are never registered in the cache (see
mountZipStream) in ZipEntryContext.
s/mountZipStream/mountZipfile/g
--
Jason T. Greene
JBoss, a division of Red Hat