Yes, I understand that one approach is to explode my deployment in
standalone/data/content/xx/yyy/war
where xx refers to first 2 characters of sha1 hash, based of composite data, byte array,
yyy refers to remaining characters.
I am trying to explore if there is a way where I do not need to explode the war and just make use of the already exploded war. I may have many war and ears in my app server, and to scan for each of the dependencies, it would be better if I could just make use of the /tmp folder instead of exploding all these every time I want to scan.
In the tmp folder the exploded wars / ears will each be in a folder "content-" + some string of characters.
Are the characters added to the directory name random or there is a pattern stored somewhere that will associate them to the original WAR/EAR.
I was only able to find that deployment3423534 and temp34543645 which care created under standalone/tmp/vfs are random
private static final Random rng = new Random();
static String createTempName(String prefix, String suffix) { return prefix + Long.toHexString(rng.nextLong()) + suffix;}
I'm trying to find what creates the "content-123", "content-xws" directories and whether it can be matched with original war or ear.
Happy to dig into source code if I could have some direction.