Web Application
Web Application
There is a web application in progress, it is mostly done, but lacks the ability to be configured!
Basically it will use the same configuration file (I'm not a huge fan of JNDI - it has it's place). Possibly with a JNDIable way to configure which property file to use.
Purpose
The web application version of maven-proxy has always been the redheaded stepchild of the maven-proxy line. I (bwalding) personally prefer using a jetty instance for it.
However I am aware that some people prefer the web application version - and so I need to find out how and why.
- Why don't you use the standalone version?
- What's the best way to configure it? (all properties in the jndi context / jndi property pointing at a config file on file system / jndi property pointing at a file in the context / hardwired filename inside the exploded war (eg WEB-INF/maven-proxy.properties) - my preference is for 1 and then 2 (with maven-proxy. as a prefix for all properties). 3 seems dirty to me - MAVENPROXY-14 - getRealPath doesn't work unless the WAR is exploded in tomcat).
- Which container are you using?
Once we've decided on the most appropriate configuration method, I'll update the war build and it will be fully supported. For the time being... it languishes.