I've followed Jinmei's suggestion and initial testing looks great. I'm going to rejigger existing unit tests to use parameters so it'll test both geode and gemfire-api (as well as management), fire off a precheckin, and see how it plays out.
On Tue, Jul 26, 2016 at 3:39 PM, Jinmei Liao <jil...@pivotal.io> wrote: > It turns out in ManagementAgent or RestAgent, we are using JettyHelper to > add the web apps under each specific context: > > JettyHelper.addWebApplication(httpServer, "/gemfire-api", gemfireAPIWar); > > So the solution is to add the same war file in the "/geode" context as > well. This does mean that we will use more disk space since we installed > two web apps instead of just one, but it's a quick solution, and we will > delete the old web app after a few versions. > > > > > On Tue, Jul 26, 2016 at 3:05 PM, Jens Deppe <jde...@pivotal.io> wrote: > > > Could you do a redirect instead of forwarding? > > > > --Jens > > > > > On Jul 26, 2016, at 1:57 PM, Kevin Duling <kdul...@pivotal.io> wrote: > > > > > > There is a story to rename the gemfire-api (Developer API) and gemfire > > > (Management API) to geode and geode-mgmt, respectively. > > > > > > The change itself is rather trivial. Just a couple web.xml changes, > > rename > > > gemfire-api-servlet.xml, and update unit tests. > > > > > > The non-trivial part is still supporting other applications that are > > > expecting to access the old URLs. The servlets are injected in to > Jetty > > > with a context, they don't just sit on the default / path. As a > result, > > > I'm unable to do some aliasing in the servlet-mapping section of > web.xml. > > > > > > How large of an impact is this going to be? > > > > > > -- > Cheers > > Jinmei >
