You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Jürgen Weber (JIRA)" <ji...@apache.org> on 2008/02/10 19:41:07 UTC
[jira] Created: (JSPWIKI-181) Common prefix for static resources
Common prefix for static resources
----------------------------------
Key: JSPWIKI-181
URL: https://issues.apache.org/jira/browse/JSPWIKI-181
Project: JSPWiki
Issue Type: Improvement
Components: Core & storage
Affects Versions: 2.6.2
Reporter: Jürgen Weber
Priority: Minor
If you want an URL schema like
http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
JkMount /wiki* MyJKAlias
JkMount /templates* MyJKAlias
JkMount /scripts* MyJKAlias
JkMount /images* MyJKAlias
JkMount /attach* MyJKAlias
JkMount /Login.jsp* MyJKAlias
JkMount /Logout.jsp* MyJKAlias
JkMount /Search.jsp* MyJKAlias
JkMount /Comment.jsp* MyJKAlias
JkMount /Rename.jsp* MyJKAlias
JkMount /Upload.jsp* MyJKAlias
JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567531#action_12567531 ]
Janne Jalkanen commented on JSPWIKI-181:
----------------------------------------
...and that would break backwards compatibility for all the URLs. I don't think that is a good idea.
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Jürgen Weber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567479#action_12567479 ]
Jürgen Weber commented on JSPWIKI-181:
--------------------------------------
> You can just JkMount /* and be done with it.
Not if Apache should serve other things, too. Ours is frontend for JSPWiki, Bugzilla, Webalizer and lots of static docs.
So using Apache has at least two advantages:
* it's a common entry point
* it's serving port 80
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567460#action_12567460 ]
Janne Jalkanen commented on JSPWIKI-181:
----------------------------------------
You can just JkMount /* and be done with it. You do not gain any particular advantage in serving the static content through Apache anyway. You can use an alias for /scripts and move them elsewhere and force Apache to serve those if you really want to.
I'd be inclined to claim this as a WontFix, since it would cause breakage of all the URLs for all the users.
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Jürgen Weber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567481#action_12567481 ]
Jürgen Weber commented on JSPWIKI-181:
--------------------------------------
Well, if I could assume that everything from JSPWiki is below /wiki (the servlet) or /wikistatic (everything else) it would be fine (and we're at the idea of this bug ;-)
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: org.safehaus.uuid.UUID vs. java.util.UUID
Posted by Andrew Jaquith <an...@mac.com>.
Murray --
The version of CookieAuthLoginModule for the current 2.8 builds use
the built-in Java 5 class java.util.UUID. So you must be looking at an
earlier version...
PS. I also used the built-in Java 5 version for the generating UIDs
for user profiles. Specifically, AbstractUserDatabase uses it also...
Andrew
On Jun 10, 2008, at 12:06 AM, Murray Altheim wrote:
> Hi,
>
> Given that Java 5 includes java.util.UUID I'm wondering why we're
> using
> the jug-asl-2.0.0.jar file (org.safehaus.uuid.UUID) and if it can be
> replaced by using the native one in Java. Lighten the load, etc. Is
> there a compelling reason to use the non-Java version?
>
> I note in CookieAuthenticationLoginModule.java that there's a note to
> replace this in 3.0 -- any reason why the wait? Or is this just due to
> workload/time available?
>
> Cheers,
>
> Murray
>
> ...........................................................................
> Murray Altheim <murray07 at altheim.com>
> === = =
> http://www.altheim.com/murray/ =
> = ===
> SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk =
> = = =
>
> Boundless wind and moon - the eye within eyes,
> Inexhaustible heaven and earth - the light beyond light,
> The willow dark, the flower bright - ten thousand houses,
> Knock at any door - there's one who will respond.
> -- The Blue Cliff Record
Re: org.safehaus.uuid.UUID vs. java.util.UUID
Posted by Murray Altheim <mu...@altheim.com>.
Janne Jalkanen wrote:
>
> If you take a closer look you'll see that 2.7.x builds already use the
> JDK5 version and got rid of the jug library.
Ah, yes, I was specifically looking at my current 2.6.2 install's lib
directory, still playing catch-up with newer builds. Okay, good. Thanks
all for the clarification.
Murray
...........................................................................
Murray Altheim <murray07 at altheim.com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
Re: org.safehaus.uuid.UUID vs. java.util.UUID
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
If you take a closer look you'll see that 2.7.x builds already use
the JDK5 version and got rid of the jug library.
/Janne
On 10 Jun 2008, at 07:06, Murray Altheim wrote:
> Hi,
>
> Given that Java 5 includes java.util.UUID I'm wondering why we're
> using
> the jug-asl-2.0.0.jar file (org.safehaus.uuid.UUID) and if it can be
> replaced by using the native one in Java. Lighten the load, etc. Is
> there a compelling reason to use the non-Java version?
>
> I note in CookieAuthenticationLoginModule.java that there's a note to
> replace this in 3.0 -- any reason why the wait? Or is this just due to
> workload/time available?
>
> Cheers,
>
> Murray
>
> ......................................................................
> .....
> Murray Altheim <murray07 at altheim.com>
> === = =
> http://www.altheim.com/murray/
> = = ===
> SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk
> = = = =
>
> Boundless wind and moon - the eye within eyes,
> Inexhaustible heaven and earth - the light beyond light,
> The willow dark, the flower bright - ten thousand houses,
> Knock at any door - there's one who will respond.
> -- The Blue Cliff Record
org.safehaus.uuid.UUID vs. java.util.UUID
Posted by Murray Altheim <mu...@altheim.com>.
Hi,
Given that Java 5 includes java.util.UUID I'm wondering why we're using
the jug-asl-2.0.0.jar file (org.safehaus.uuid.UUID) and if it can be
replaced by using the native one in Java. Lighten the load, etc. Is
there a compelling reason to use the non-Java version?
I note in CookieAuthenticationLoginModule.java that there's a note to
replace this in 3.0 -- any reason why the wait? Or is this just due to
workload/time available?
Cheers,
Murray
...........................................................................
Murray Altheim <murray07 at altheim.com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
Re: [jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by Janne Jalkanen <Ja...@ecyrd.com>.
I'm not very fond of a structure where static and dynamic files are
in separate directories. I would much rather see a structure where
templates can be deployed as single JAR files (to make upgrades/
installations easy).
/Janne
On 9 Jun 2008, at 22:00, Andrew Jaquith wrote:
> Personally I don't see how we can fix this in the 2.7/2.8 release
> cycle. Too hard. It probably would be good to eventually move
> everything to a /static subcontext, though.
>
> On Jun 8, 2008, at 1:11 PM, Harry Metske (JIRA) wrote:
>
>>
>> [ https://issues.apache.org/jira/browse/JSPWIKI-181?
>> page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
>> tabpanel&focusedCommentId=12603409#action_12603409 ]
>>
>> Harry Metske commented on JSPWIKI-181:
>> --------------------------------------
>>
>> Having a clear separation between static and non-static content by
>> prefix would be great, but it isn't there at the moment. Getting
>> there is not so easy according to Janne.
>> And has Jürgen tried the instructions Andrew mentioned (http://
>> www.jspwiki.org/wiki/DeploymentOptimizations) ?
>> In the first place I would try to switch from mod_jk to
>> mod_proxy_ajp.
>>
>>> Common prefix for static resources
>>> ----------------------------------
>>>
>>> Key: JSPWIKI-181
>>> URL: https://issues.apache.org/jira/browse/
>>> JSPWIKI-181
>>> Project: JSPWiki
>>> Issue Type: Improvement
>>> Components: Core & storage
>>> Affects Versions: 2.6.2
>>> Reporter: Jürgen Weber
>>> Priority: Minor
>>>
>>> If you want an URL schema like
>>> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
>>> i.e. have JSPWiki as root context, and if you additionally want
>>> to have Apache as frontend (to avoid the application server
>>> having Unix root rights to listen on port 80), you have to
>>> configure in Apache's http.conf which URLs should go to mod_jk.
>>> Right now this is a rather long list. This could be made easier
>>> if the static content were below a common folder (e.g.
>>> wikistatic) and if the remaining .JSPs would be done by the wiki
>>> servlet.
>>> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
>>> JkMount /wiki* MyJKAlias
>>> JkMount /templates* MyJKAlias
>>> JkMount /scripts* MyJKAlias
>>> JkMount /images* MyJKAlias
>>> JkMount /attach* MyJKAlias
>>> JkMount /Login.jsp* MyJKAlias
>>> JkMount /Logout.jsp* MyJKAlias
>>> JkMount /Search.jsp* MyJKAlias
>>> JkMount /Comment.jsp* MyJKAlias
>>> JkMount /Rename.jsp* MyJKAlias
>>> JkMount /Upload.jsp* MyJKAlias
>>> JkMount /UserPreferences.jsp*
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
Re: [jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by Andrew Jaquith <an...@mac.com>.
Personally I don't see how we can fix this in the 2.7/2.8 release
cycle. Too hard. It probably would be good to eventually move
everything to a /static subcontext, though.
On Jun 8, 2008, at 1:11 PM, Harry Metske (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603409
> #action_12603409 ]
>
> Harry Metske commented on JSPWIKI-181:
> --------------------------------------
>
> Having a clear separation between static and non-static content by
> prefix would be great, but it isn't there at the moment. Getting
> there is not so easy according to Janne.
> And has Jürgen tried the instructions Andrew mentioned (http://www.jspwiki.org/wiki/DeploymentOptimizations
> ) ?
> In the first place I would try to switch from mod_jk to mod_proxy_ajp.
>
>> Common prefix for static resources
>> ----------------------------------
>>
>> Key: JSPWIKI-181
>> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
>> Project: JSPWiki
>> Issue Type: Improvement
>> Components: Core & storage
>> Affects Versions: 2.6.2
>> Reporter: Jürgen Weber
>> Priority: Minor
>>
>> If you want an URL schema like
>> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
>> i.e. have JSPWiki as root context, and if you additionally want to
>> have Apache as frontend (to avoid the application server having
>> Unix root rights to listen on port 80), you have to configure in
>> Apache's http.conf which URLs should go to mod_jk.
>> Right now this is a rather long list. This could be made easier if
>> the static content were below a common folder (e.g. wikistatic) and
>> if the remaining .JSPs would be done by the wiki servlet.
>> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
>> JkMount /wiki* MyJKAlias
>> JkMount /templates* MyJKAlias
>> JkMount /scripts* MyJKAlias
>> JkMount /images* MyJKAlias
>> JkMount /attach* MyJKAlias
>> JkMount /Login.jsp* MyJKAlias
>> JkMount /Logout.jsp* MyJKAlias
>> JkMount /Search.jsp* MyJKAlias
>> JkMount /Comment.jsp* MyJKAlias
>> JkMount /Rename.jsp* MyJKAlias
>> JkMount /Upload.jsp* MyJKAlias
>> JkMount /UserPreferences.jsp*
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Harry Metske (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603409#action_12603409 ]
Harry Metske commented on JSPWIKI-181:
--------------------------------------
Having a clear separation between static and non-static content by prefix would be great, but it isn't there at the moment. Getting there is not so easy according to Janne.
And has Jürgen tried the instructions Andrew mentioned (http://www.jspwiki.org/wiki/DeploymentOptimizations) ?
In the first place I would try to switch from mod_jk to mod_proxy_ajp.
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567480#action_12567480 ]
Janne Jalkanen commented on JSPWIKI-181:
----------------------------------------
If you want to put jspwiki in root, I would strongly recommend you to put it in a virtualhost (e.g. wiki.myorg.org). That makes the setup a breeze. Or, put your static stuff in static.myorg.org. Doesn't matter.
You see, we can't guarantee there won't be name conflicts later on - if we happen to create a statistics plugin, and it writes some stuff in /statistics, you might get a clash in your setup with Webalizer or whatever.
It's really best if you keep the namespaces separated - assuming that JSPWiki uses a particular directory structure is just asking for trouble.
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Jürgen Weber (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12611996#action_12611996 ]
Jürgen Weber commented on JSPWIKI-181:
--------------------------------------
Andrew's page "Deployment Optimizations" is for a JSPWiki that is in a /jspwiki context, it does not work for a ROOT installation, i.e.
http://myhost/ThisIsAWikiPage
This is exactly my problem that for a ROOT installation there is no common prefix like /jspwiki
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603394#action_12603394 ]
Janne Jalkanen commented on JSPWIKI-181:
----------------------------------------
What shall we do with this?
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-181) Common prefix for static resources
Posted by "Andrew Jaquith (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567764#action_12567764 ]
Andrew Jaquith commented on JSPWIKI-181:
----------------------------------------
Jürgen --
See my jspwiki.org page "Deployment Optimizations" at http://www.jspwiki.org/wiki/DeploymentOptimizations.
It shows how you can build a very simple mod_jk ruleset, in combination with the Ant "staticzip" target. I have not verified the instructions with 2.6, but they *should* work plus or minus a few tweaks.
> Common prefix for static resources
> ----------------------------------
>
> Key: JSPWIKI-181
> URL: https://issues.apache.org/jira/browse/JSPWIKI-181
> Project: JSPWiki
> Issue Type: Improvement
> Components: Core & storage
> Affects Versions: 2.6.2
> Reporter: Jürgen Weber
> Priority: Minor
>
> If you want an URL schema like
> http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> i.e. have JSPWiki as root context, and if you additionally want to have Apache as frontend (to avoid the application server having Unix root rights to listen on port 80), you have to configure in Apache's http.conf which URLs should go to mod_jk.
> Right now this is a rather long list. This could be made easier if the static content were below a common folder (e.g. wikistatic) and if the remaining .JSPs would be done by the wiki servlet.
> See also http://www.jspwiki.org/wiki/JSPWikiAsRootContextWithApache
> JkMount /wiki* MyJKAlias
> JkMount /templates* MyJKAlias
> JkMount /scripts* MyJKAlias
> JkMount /images* MyJKAlias
> JkMount /attach* MyJKAlias
> JkMount /Login.jsp* MyJKAlias
> JkMount /Logout.jsp* MyJKAlias
> JkMount /Search.jsp* MyJKAlias
> JkMount /Comment.jsp* MyJKAlias
> JkMount /Rename.jsp* MyJKAlias
> JkMount /Upload.jsp* MyJKAlias
> JkMount /UserPreferences.jsp*
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.