The best approach is to leave the WAR as named xwiki and configure Tomcat in
server.xml to deploy the application.
I deployed xwiki.war into webapps.
www.justiceintheworkplace.org executes
the application xwiki because of the <Context
path=""docBase="xwiki"
below
<Host appBase="webapps" name="justiceintheworkplace.org"
unpackWARs="true"
autoDeploy="true">
<Alias>www.justiceintheworkplace.org</Alias>
<Context path="" docBase="xwiki" debug="0"
reloadable="true"/>
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="justiceintheworkplace.org." suffix=".txt"
timestamp="true"/>
</Host>
martingales wrote:
I wish to rename the WAR so I can deploy under Tomcat and access as
http://localhost:8080/mywiki
I believe that I need to do some configuration beyond renaming the WAR.
For instance, I have trouble importing the XAR because:
http://localhost:8080/mywiki/bin/adim/XWiki/XWikiPreferences resolves to:
http://localhost:8080/xwiki/bin/objectadd/XWiki/XWikiPreferences?classname=…
and the error message is: The requested resource
(/xwiki/bin/objectadd/XWiki/XWikiPreferences) is not available.
--
View this message in context:
http://www.nabble.com/Configuration-necessary-to-rename-WAR---Deploy--tf362…
Sent from the XWiki- Users mailing list archive at
Nabble.com.