It's all internal implementation details of the server. What's the reason that you are checking that (temporary) folder path for jars and why do you expect it to be in a specific way?
I am using Cocoon page publishing framework. Some how its not able to recognize classes inside utility.jar. This utility.jar is part of EAR file.
Here is EAR structure
|--- EJB Jar
Utility.jar has common classes which are shared between WAR and EJB jar.
To make it work for Cocoon I would like to specify relative path for Utility.jar in web.xml for Cocoon.
If folder structure remain same during deployment then I can give relative path.
Create a lib folder in the .ear and put the utility.jar within that .ear/lib folder. It will be available to both the war and the EJB jar.
You can also create a custom module for such jars , and use it everywhere.