Re: Parallel deployment URL issue

2015-10-02 Thread Chris Gamache
Unfortunately, pre-encoding the "##" doesn't work. :( I have a reasonable workaround with a separate context.xml. On top of that, it's pretty simple to patch tomcat to use a different version marker other than "##". I figure if I get desperate I can patch, build, and run my own. On Thu, Oct 1,

Re: Parallel deployment URL issue

2015-10-02 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 10/1/15 5:26 PM, Chris Gamache wrote: > I didn't know that you could do that for parallel deployment! > > A quick follow-up set of questions: > > Up until now I was counting on manager and tomcat's unpackWAR > handling the nuts and bolts

Re: Parallel deployment URL issue

2015-10-01 Thread Aurélien Terrestris
Hello maybe the Java documentation is badly written, because it is saying ( http://docs.oracle.com/javase/7/docs/api/java/io/File.html#toURL%28%29 ) : "This method does not automatically escape characters that are illegal in URLs." # character is not illegal, but reserved (see gen-delims definiti

Re: Parallel deployment URL issue

2015-10-01 Thread Chris Gamache
I didn't know that you could do that for parallel deployment! A quick follow-up set of questions: Up until now I was counting on manager and tomcat's unpackWAR handling the nuts and bolts of the deploy process. Even though the warfile is named yourWar-2.war, if I allow tomcat to unpack the wa

Re: Parallel deployment URL issue

2015-10-01 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Chris, On 10/1/15 11:51 AM, Chris Gamache wrote: > Hi all, > > I'm stuck using axis2-1.5.4. > > Here's what I think is happening: > > Axis2 does this sort of container-in-a-container thing. It creates > its own classloader and pulls in all of its

Parallel deployment URL issue

2015-10-01 Thread Chris Gamache
Hi all, I'm stuck using axis2-1.5.4. Here's what I think is happening: Axis2 does this sort of container-in-a-container thing. It creates its own classloader and pulls in all of its jar libraries dynamically. The problem is that it uses a java.net.URL to target the files. This would be fine exce