Support war names that contain # symbol denoting sub path.

[TonyWeston]

Tomcat supports contexts that have paths with many sub paths.

As you know, app.war will be deployed to context /app

However, it is also possible to deploy a war to a context that may have multiple sub paths.

app#sub1.war is deployed to context /app/sub1
app#sub2.war is deployed to context /app/sub2
app#sub2#abc.war is deployed to context /app/sub2/abc

Also versions of apps can be specified by using two hash's in the name
app##12.war is deployed to /app

See here for more details:
https://tomcat.apache.org/tomcat-8.0-doc/config/context.html#Naming

Currently, psiprobe struggles with war files named this way.

[hazendaz]

@TonyWeston Can you provide details as to what fails? This is vague at best so I need full description of what is not supported including stack traces. Also any pull request you can provide that fixes the situation is most appreciated. If my memory serves me, I thought we addressed this a couple years back so I'm not clear what the issue is with current release.

[TonyWeston]

Ok, steps to reproduce, on Psiprobe 3.2.0 (built at 2018-12-20T22:06:41Z)

1. Create the simpliest 'hello world' webapp, export it as app.war
2. Deploy this in psiprobe, to verify it works as expected.
3. Rename the war to app#sub1.war . deploy this in psiprobe.
4. Psiprobe shows the error "/app#sub1 was not installed". However, it is actually deployed as shown in the Applications tab, and also /app/sub1/ responds as expected.
5. Attempt to undeploy this app from Psiprobe applications tab
6. Psiprobe returns no error, however /app/sub1 is not undeployed.

[TonyWeston]

Feel free to use this war file for test purposes.

app#sub1.zip

[wlusink]

I have the issue with the two hash marks for the version.
When I deploy a file like app##1.0.war in the apache manager, it will be deployed to /app and in the manager it will show 1.0 in the version column.
When I try to deploy app##1.1.war in the apache manager, it will fail, saying that there is already an application at /app.

However, in psi probe, when I first deploy app##1.0.war, the app will be deployed to /app, but in psi probe its name will be app##1.0.war, and the link will be /app##1.0. The link will open the application because of the hash in the link.
Then, when I deploy app##1.1.war in psi probe, it will deploy this app alongside the app##1.0.war.
When I now look in manager, I have these two applications installed alongside each other, but there is only one link, namely /app.

As a solution, I think it would be good if psi probe would implement the ##version naming convention. And also show this version in the Applications tab. Exactly like in the apache manager.

How else can I see an application's version number in psi probe?