[
https://issues.apache.org/jira/browse/JSPWIKI-139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18134409#comment-18134409
]
Arturo Bernal commented on JSPWIKI-139:
---------------------------------------
Checked with the current build (master plus a small unrelated change, Tomcat
10.1, Chrome). To answer the question of the comment of 2025: the war does run
under a context path other than the root. I deployed it as /wiki: the pages are
served there and not at the root, every link of a page carries the prefix (the
links to Edit.jsp, Login.jsp, PageInfo.jsp, Upload.jsp and the edit links of
the sections), the cookie of the user preferences is set with the path /wiki,
and saving and reading the preferences works.
What this report asks for is something else: putting the JSPs in a subdirectory
of the web application so that the engine can be embedded in another webapp,
with addresses such as host/webapp/somesubdir/Wiki.jsp?page=Foo. I did not try
that, and the attached patches are from 2008 against CVS, so I did not check
them against the current code. So the context path part works today and the
embedding part is untested. Leaving the issue open.
> Allow jspwiki pages to be at locations other than webapp root (for embedding)
> -----------------------------------------------------------------------------
>
> Key: JSPWIKI-139
> URL: https://issues.apache.org/jira/browse/JSPWIKI-139
> Project: JSPWiki
> Issue Type: Improvement
> Affects Versions: 2.6.1
> Reporter: Simon Kitching
> Priority: Minor
> Fix For: STRIPES/JCR-3.1
>
> Attachments: TemplateManager.patch, WikiEngine.patch
>
>
> The attached patches allow jspwiki pages to be deployed anywhere within a
> webapp. In particular, the jspwiki engine can now be embedded within another
> webapp and the pages placed in a subdirectory while still rendering in the
> normal manner (http://host/webapp/somesubdir/Wiki.jsp?page=Foo).
> Note that embedded jspwiki usage has not been extensively tested; there may
> be more patches required to allow full functionality. However this gets the
> basics working at least.
> Patches are against cvs trunk as of about 15 Jan 2008.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
