[ https://issues.apache.org/jira/browse/GEODE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397847#comment-15397847 ]
Kevin Duling edited comment on GEODE-1467 at 7/28/16 5:34 PM: -------------------------------------------------------------- Added the servlets to Jetty twice as a temporary solution in order to support both contexts for a period of time. Updated DUnit tests to test both URL endpoints. gemfire-api became geode gemfire became geode-mgmt was (Author: kduling): Added the servlets to Jetty twice as a temporary solution in order to support both contexts for a period of time. Updated DUnit tests to test both URL endpoints. > Branding: Rename servlet URLs from gemfire to geode > --------------------------------------------------- > > Key: GEODE-1467 > URL: https://issues.apache.org/jira/browse/GEODE-1467 > Project: Geode > Issue Type: Improvement > Components: docs, rest (admin), rest (dev) > Reporter: Nitin Lamba > Assignee: Kevin Duling > > There are a few locations where gemfire references are used (excluding > package hierarchy covered in GEODE-37): > 1. servlet URLs for Dev REST (gemfire-api) and Mgmt REST (gemfire/v1) > 2. extension modules (http session mgmt) > 3. others (spring-data?) > (2) and (3) can be hairy as it may impact existing applications. A change > post 1.0 would create complexity, therefore, should be carefully considered > for 1.0 release. -- This message was sent by Atlassian JIRA (v6.3.4#6332)