Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-46) was last changed on 15-Nov-2011 11:51 by xiaochang619  

This page was created on 02-Jun-2003 16:32 by JanneJalkanen

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 1 changed one line
!!Jspwiki and the MVC model
__THIS IS STILL INCOMPLETE; PLEASE ADD TO IT__
It'd be nice to see a good condensed page highlighting the changes from one release to another. Unfortunately one doesn't exist.
At line 3 changed one line
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".
At the moment your best bet is to read the Change Log. And if someone wants to maintain the Release Notes on this wiki, I don't mind.
At line 5 changed one line
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.
-- JanneJalkanen
At line 7 removed one line
!!Merge or copy?
At line 9 changed 6 lines
The ReleaseNotes suggest that you make a brand new install and copy your old configuration over it.
You should consider merging files and directories instead. Merging is better then copying. A simple copy may cause you to loose any new text or properties that might have been introduced. Therefore,
*in the $JSPWIKI_HOME/WEB-INF directory
**merge the contents of your {{jspwiki.properties}} file.
*in the $JSPWIKI_HOME/WEB-INF/lib and $JSPWIKI_HOME/WEB-INF/classes directories
**merge your plugin libraries and filter files
The most secure way to upgrade is to simply merge your
configuration files from your previous installation to
the location of your new installation.
At line 13 added 2 lines
You may want to make a backup of your previous installation,
undeploy it and deploy the new installation from scratch.
At line 17 changed one line
__THIS IS STILL INCOMPLETE; PLEASE ADD TO IT__
!!Merge or copy?
At line 19 changed one line
So, you are running an older version of JSPWiki, and have decided to upgrade? Good for you.
The ReleaseNotes suggest that you make a brand new install and copy your old configuration over it. You should consider merging files and directories instead. Merging is better then copying. A simple copy may cause you to loose any new text or properties that might have been introduced. If you don't know how to automate the merge process, you may have to manually compare each configuration file for differences. If you use Ant, this Ant Plugin task is recommended. Code is available from [here |http://www.hydrogenline.com/ant/ant_md.zip]
At line 21 changed one line
Here are some instructions on how to actually do the upgrade as smoothly as possible.
!!Upgrading from the same release (From 2.x.y to 2.x.z ):
When upgrading to the same version, both top-level JSP files and default files are compatible. Basically you'll just need to upgrade your changes to the files themselves. Merging is done from your backup of the previous installation ($JSPWIKI_HOME)to the location of your new installation.
At line 23 changed one line
The notation $JSPWIKI_HOME will denote the place where the old JSPWiki version is installed.
* Install the JSP files (top-level and
the default template)
** Copy all top-level JSP files (Wiki.jsp, Edit.jsp, etc) from $JSPWIKI_HOME/
** Copy all default template JSP files from $JSPWIKI_HOME/$myDefault
* Install the set of JAR files.
** Copy all of the .jar -files into your $JSPWIKI_HOME/WEB-INF/lib
At line 25 changed one line
!!Notes on Upgrading to 2.3.x/2.4.x
The following configuration files have typically been modified in the old version and need to be merged with the new files:
At line 27 changed 5 lines
__NOTE:__ This is safer then copying over your previous installation as suggested below, but
* __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.
* Compare the contents of the following files:
*in the $JSPWIKI_HOME/WEB-INF directory
** jspwiki.properties
At line 39 added 2 lines
** groupdatabase.xml
** userdatabase.xml
At line 38 changed one line
The attached Ruby script can help in that task, as it will detect version conflicts.
*in the $JSPWIKI_HOME/WEB-INF/lib and $JSPWIKI_HOME/WEB-INF/classes directories
**merge your plugin libraries and filter files
At line 40 changed one line
!!From 2.0.x to 2.0.y
!!Important:
*In JSPWiki 2.3+, JavaCryptographyArchitecture[JCA|http://java.sun.com/products/archive/j2se-eol.html]is used. If the jspwiki.jks file is missing, the server won't recognize the JSPWiki.jar file as secured. Therefore, move your jspwiki.jks file from for example {{$JSPWIKI_BUILD_HOME/etc/jspwiki.jks}}) to the {{$JSPWIKI_HOME/WEB-INF}} directory on the server. The JSPWiki.jar file is now signed so this step is crucial; failing to do so will cause the new security checks to fail. For more info see:[KeyStore|http://java.sun.com/j2se/1.4.2/docs/api/java/security/KeyStore.html].
At line 42 changed one line
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.
*If you added plugins to the old tld file, be sure to include these in the new.
At line 44 changed 4 lines
* 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.
!!Upgrading from a new version (2.x version to 2.y version):
At line 49 changed one line
;:''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
The ReleaseNotes file that is in every JSPWiki distribution details the differences between the stable versions (2.0, 2.2). However, any odd-labeled version is a development version, and therefore the ReleaseNotes are not necessarily updated that well. The goals for future versions are documented [here | http://www.jspwiki.org/wiki/RoadMap]
At line 54 added 28 lines
When upgrading to a new version, *always* assume that the top-level JSP files are incompatible and *must* be upgraded every single time. View files (those under templates/) are normally kept compatible. 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.
* Please reinstall in a new directory. Then move your modified
templates into the new templates/ -directory. You MUST
have the default template in place, else things might not
work. If you have modified the default template, please
rename your old template to "mymodifications" or something.
You must NOT modify the default template anymore.
* Replace jspwiki.properties with your old configuration file.
It should run unmodified, though you might want to go through
the new file to see new options. Most specifically:
* jspwiki.baseURL is now mandatory
* jspwiki.workDir is a good idea to set
* Set jspwiki.security=off, if you don't want JSPWiki to
use its own security system. If you do, head over
to doc.jspwiki.org/2.4 for further instructions.
* You can copy your old filters.xml to WEB-INF/classes
Upgrading from earlier installations:
* Please make a complete reinstall. Your wiki pages will still be
compatible, and the configuration for the most part.
At line 59 changed 2 lines
* SystemInfo.jsp is gone. Instead, there is now a page called
"SystemInfo".
* System.jsp is gone. Instead, there is now a page called
"System".
Version Date Modified Size Author Changes ... Change note
46 15-Nov-2011 11:51 7.198 kB xiaochang619 to previous SystemInfo ==> System
45 19-Dec-2008 14:36 7.206 kB Sadness to previous | to last SystemInfo1 ==> SystemInfo
44 19-Dec-2008 14:36 7.208 kB Sadness to previous | to last SystemInfo ==> SystemInfo1
43 12-Oct-2007 06:43 7.206 kB JanneJalkanen to previous | to last
42 12-Oct-2007 03:18 7.218 kB 217.171.176.46 to previous | to last
41 26-Sep-2007 12:49 7.206 kB Claudia.Frers to previous | to last
« This page (revision-46) was last changed on 15-Nov-2011 11:51 by xiaochang619