I'm assuming you're referring to what ends up in the 'work' dir
of the tomcat-based virtualization server.
This is expected behavior when you modified a jar file in your WEB-INF dir
and/or if you're talking about a jar file in the staging area of a project.
The reason this is necessaryis that the AVMremote does
not have the ability to open file for random-access,
which is what you need when youv'e got a jar/zip file.
If your author workarea does not contain any modified
jars, then you will not see a copy of the jars you inherit
via transparency from staging. That gets virtualized away.
Cheers,
-Jon
PS:
Incidentally, the memory that author jar files would otherwise
consume in an unmodified WEB-INF is also virtualized away;
a classloader hierarchy for the virtual webapps is created that
parallels the overlay structure of the AVM stores containing them
(this is used whenever possible, to allow the virtualization server
to scale).
