This is version . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Jspwiki and the MVC model #

Our template files provide the "View", the JSPWiki.jar provides the "Model", and the top-level JSPs provide the "Controller". While the top-level JSP files are JSP (provide HTML with Java snippets".), they're actually "the backend code placed upfront" and are essentially treated as "easy- to-deploy servlets".

When upgrading to a new version, *always* assume that he top-level JSP files are incompatible and *must* be upgraded every single time. However, the view files (those under templates/) we try to keep compatible. You may lose functionality if you don't upgrade the template, but in general not even that after the initial stable has been released. There might be bug fixes, though, which is why it is a good idea to upgrade the default template as well. If you want to "freeze" the template, make a copy of the default template, call it "mytemplate" and use that. JSPWiki will then fall back to the default template in case any new JSP files are added.

THIS IS STILL INCOMPLETE; PLEASE ADD TO IT

So, you are running an older version of JSPWiki, and have decided to upgrade? Good for you.

Here are some instructions on how to actually do the upgrade as smoothly as possible.

The notation $JSPWIKI_HOME will denote the place where the old JSPWiki version is installed.

Notes on Upgrading to 2.3.x/2.4.x#

NOTE: The ReleaseNotes suggest that you make a brand new install and copy your old configuration over it. This is safer then copying over your previous installation as suggested below, but you should consider merging files and directories instead.

  • MAKE SURE you copy the jspwiki.jks file from the distribution into your $JSPWIKI_HOME/WEB-INF directory. The JSPWiki.jar file is now signed so this step is crucial; failing to do so will cause the new security checks to fail.
  • Still in the $JSPWIKI_HOME/WEB-INF directory, merge the contents of your jspwiki.properties file. Merging is better then copying as you don't want to lose the new properties that might have been introduced.
  • Compare the contents of the following files:
    • web.xml
    • jspwiki.policy
    • jspwiki.jaas
    • jspwiki.tld
    • oscache.properties
  • Merge your plugin libraries and filter files from the $JSPWIKI_HOME/WEB-INF/lib and $JSPWIKI_HOME/WEB-INF/classes directories. The attached Ruby script can help in that task, as it will detect version conflicts.

From 2.0.x to 2.0.y#

All of the 2.0.x releases should be somewhat compatible with each other, so basically you'll just need to upgrade the files themselves.

  • Copy all of the .jar -files from the distribution into your $JSPWIKI_HOME/WEB-INF/lib
  • Copy the jspwiki.tld file to $JSPWIKI_HOME/WEB-INF/
  • Copy all of the main JSP files (Wiki.jsp, Edit.jsp, etc) to $JSPWIKI_HOME/
  • Check out the ReleaseNotes -file for anything else.
I used these same instructions to go from a 2.2.x to 2.2.x. Beware when copying the tld file that you update the new file with any changes you might have made to the old file (i.e. added plugins) --chaworth

From 1.8.x to 2.0.x#

  • Providers now sleep in a different package. You must change your "jspwiki.pageProvider" setting.
  • CachingProvider is no longer set explicitly. You must use the new "jspwiki.usePageCache" property instead.
  • All HTML code should now go into *Template.jsp instead of Wiki.jsp and the other main JSP pages.
  • SystemInfo.jsp is gone. Instead, there is now a page called "SystemInfo".

So, the best way to do the update is to simply save your "jspwiki.properties", and "web.xml" files to some safe location, DELETE your previous installation, and install it again from scratch. However, after this your templates should be easily modifiable, and you never again have to resort to such drastic measures again... We hope.

Troubleshooting#

I did the upgrade from 2.0.45 to 2.0.48 just like this... And it seems that the upgrade took hold (much faster)... But the version still says I'm on .45... any clues? -- MatthewSimpson

Remove the compiled JSP files. For Tomcat, remove the $TOMCAT_HOME/work/<your web app> directory, or just touch the JSP files using touch(1).

The problem is that when you upgrade, the compiled JSP files contain the compiled version of the version number as well... This problem has actually been solved in 2.1.

If you've done an upgrade and nobody seems to have any permissions, make sure you've copied the Java KeyStore file $JSPWIKI_BUILD_HOME/etc/jspwiki.jks) to the $JSPWIKI_HOME/WEB-INF directory on the server. JSPWiki 2.3+ uses the JavaCryptographyArchitecture JCA. Absent the jspwiki.jks file, the server won't recognize the JSPWiki.jar file as secured. -- MurrayAltheim

I upgraded from 2.2.33 to 2.4.71 and the search is not working properly. For example a word that can be found in the main page cannot be found by the search function. However, when I modified the main page, the search was able to find it. So it seems like there is some kind of refresh required. How am I able to do that so that I don't have to open and save every page?

I found the solution to this myself. It had nothing to do with the upgrade. I just had to define the working directory to the jspwiki.properties file and the search started to work just fine.

Add new attachment

Only authorized users are allowed to upload new attachments.
« This particular version was published on 25-Sep-2007 14:24 by 90.184.134.197.