JSPWiki
  1. JSPWiki
  2. JSPWIKI-606

Make JSPWiki work on Google App Engine

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.8.3
    • Fix Version/s: 3.1
    • Component/s: None
    • Labels:
      None

      Activity

      Hide
      Florian Holeczek added a comment -

      Any opinions on this improvement? Harry, AFAIR you've got some AppEngine know-how, WDYT?

      Show
      Florian Holeczek added a comment - Any opinions on this improvement? Harry, AFAIR you've got some AppEngine know-how, WDYT?
      Hide
      Andrew Jaquith added a comment -

      Unless the submitter has a specific patch ready that will allow 2.8.3 to run on Google App Engine, I recommend this be considered as an enhancement for 3.0 instead, not for the 2.8 branch. Any changes we make to 2.8 should be limited to bug fixes at this point.

      Show
      Andrew Jaquith added a comment - Unless the submitter has a specific patch ready that will allow 2.8.3 to run on Google App Engine, I recommend this be considered as an enhancement for 3.0 instead, not for the 2.8 branch. Any changes we make to 2.8 should be limited to bug fixes at this point.
      Hide
      Harry Metske added a comment -

      This is indeed a considerable investment.
      See http://code.google.com/intl/nl/appengine/docs/java/overview.html for an overview.

      The GAE (GoogleAppEngine) had been designed for massive scalability, so you can never rely on anything stored on one host.
      Some things to consider:

      • you need a GAE Eclipse plugin for development
      • you cannot write to the filesystem
      • cannot open sockets or access other hosts directly (have to use Google' s URLFetch service, which is limited to port 80/443)
      • no access to system calls
      • cannot create threads
      • cannot use java.util.Timer
      • you cannot determine the system's hostname
      • there is a JRE Class white list : http://code.google.com/intl/nl/appengine/docs/java/jrewhitelist.html
      • storing data should be done with JDO
      • I don't know if there are any licensing issues (you have to include Google Code in the build)
      • for logging, you have to use java.util.logging (Google implemented version probably)

      I really like the concept....if you build from scratch, but porting JSPWiki is quite a challenge.
      For example, not being able to write files is such a restriction, we might overcome it for just JSPWiki, but how about all the libraries we are using (log4j, lucene, priha) ?

      Show
      Harry Metske added a comment - This is indeed a considerable investment. See http://code.google.com/intl/nl/appengine/docs/java/overview.html for an overview. The GAE (GoogleAppEngine) had been designed for massive scalability, so you can never rely on anything stored on one host. Some things to consider: you need a GAE Eclipse plugin for development you cannot write to the filesystem cannot open sockets or access other hosts directly (have to use Google' s URLFetch service, which is limited to port 80/443) no access to system calls cannot create threads cannot use java.util.Timer you cannot determine the system's hostname there is a JRE Class white list : http://code.google.com/intl/nl/appengine/docs/java/jrewhitelist.html storing data should be done with JDO I don't know if there are any licensing issues (you have to include Google Code in the build) for logging, you have to use java.util.logging (Google implemented version probably) I really like the concept....if you build from scratch, but porting JSPWiki is quite a challenge. For example, not being able to write files is such a restriction, we might overcome it for just JSPWiki, but how about all the libraries we are using (log4j, lucene, priha) ?
      Hide
      Harry Metske added a comment -

      I consider this requirement as undo-able in the available dev. hours we have, and propose to close it as WONTFIX in a few days.

      Show
      Harry Metske added a comment - I consider this requirement as undo-able in the available dev. hours we have, and propose to close it as WONTFIX in a few days.

        People

        • Assignee:
          Harry Metske
          Reporter:
          Elad Mallel
        • Votes:
          0 Vote for this issue
          Watchers:
          0 Start watching this issue

          Dates

          • Created:
            Updated:
            Resolved:

            Development