Jetspeed 2
  1. Jetspeed 2
  2. JS2-891

Move the site pages out of resources into a directory outside the web applicaiton

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.0
    • Component/s: Assembly/Configuration
    • Labels:
      None

      Description

      It would be better if the Jetspeed file system "site" wsa moved out of the WEB-INF/pages directory, and instead put in another directory on the file system.
      Web applications should not have writable resources stored in the web application

      1. JS2-891.patch
        3 kB
        Jeroen Hoffman

        Activity

        Hide
        Jeroen Hoffman added a comment -

        Attached a patch for the installer that moves the pages dir to <tomcat>/pages and logs to <tomcat>/logs/jetspeed.

        Show
        Jeroen Hoffman added a comment - Attached a patch for the installer that moves the pages dir to <tomcat>/pages and logs to <tomcat>/logs/jetspeed.
        Hide
        Mansour Al Akeel added a comment -

        Ok, I agree with David and with Vivek.
        I don't know why I keep on thinking about distributing JS2 in the future as a war file. I totally missed the point that it will always be with the installer.
        Yes, in this case it's a better idea to move the pages out of the web app, and during the installatin have a default with the option to change the location.

        Show
        Mansour Al Akeel added a comment - Ok, I agree with David and with Vivek. I don't know why I keep on thinking about distributing JS2 in the future as a war file. I totally missed the point that it will always be with the installer. Yes, in this case it's a better idea to move the pages out of the web app, and during the installatin have a default with the option to change the location.
        Hide
        Vivek Kumar added a comment -

        I agree with David. all the these resources should be moved out.

        Show
        Vivek Kumar added a comment - I agree with David. all the these resources should be moved out.
        Hide
        David Sean Taylor added a comment -

        I'd like to see the upcoming release take this approach by default with the installer. I don't see any reason why we cannot make this a part of the 2.2 installer. Example: say we install into a directory named "jetspeed-2.2", then under the jetspeed-2.2 directory there would be a "pages" directory to hold the PSML pages. Similarly, log files should be stored in jetspeed-2.2/logs, and decorators under jetspeed-2.2/decorators. Any resource that can be modified should not be stored in the jetspeed resource. Anyway this is all configurable in Jetspeed without too much fuss. However if the installer promotes these habits they tend to stick

        Show
        David Sean Taylor added a comment - I'd like to see the upcoming release take this approach by default with the installer. I don't see any reason why we cannot make this a part of the 2.2 installer. Example: say we install into a directory named "jetspeed-2.2", then under the jetspeed-2.2 directory there would be a "pages" directory to hold the PSML pages. Similarly, log files should be stored in jetspeed-2.2/logs, and decorators under jetspeed-2.2/decorators. Any resource that can be modified should not be stored in the jetspeed resource. Anyway this is all configurable in Jetspeed without too much fuss. However if the installer promotes these habits they tend to stick
        Hide
        Mansour Al Akeel added a comment - - edited

        That's what I do for a deployment. I move it to /opt/tomcat/js-pages/ This helps me when upgrade of reploy the portal.
        However, moving the pages directory by default to the file system, raises another issues when installing jetspeed (ie, file premissions , extra configuration). Plus where to put it on the file system ?
        "/tmp" for linux, or "C:\WINDOWS\TEMP" on windows ... etc (ie, System.getProperty("java.io.tmpdir")), but again a temporary directory is not the safest place.

        Another possibility is the server appBase directory (ie for tomcat "tomcat/webapp" )

        Any ideas or comments?

        Show
        Mansour Al Akeel added a comment - - edited That's what I do for a deployment. I move it to /opt/tomcat/js-pages/ This helps me when upgrade of reploy the portal. However, moving the pages directory by default to the file system, raises another issues when installing jetspeed (ie, file premissions , extra configuration). Plus where to put it on the file system ? "/tmp" for linux, or "C:\WINDOWS\TEMP" on windows ... etc (ie, System.getProperty("java.io.tmpdir")), but again a temporary directory is not the safest place. Another possibility is the server appBase directory (ie for tomcat "tomcat/webapp" ) Any ideas or comments?

          People

          • Assignee:
            David Sean Taylor
            Reporter:
            David Sean Taylor
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development