Changes between Version 19 and Version 20 of ISOcat


Ignore:
Timestamp:
08/28/12 14:10:43 (12 years ago)
Author:
mwindhouwer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ISOcat

    v19 v20  
    112112 * the modules in the {{{path-to-ISOcat/develop}}} are !NetKernel modules to serve static files that in a production environment will be served by the HTTP server, e.g., Apache
    113113 * some of these static files need to be downloaded and placed in the right directory
    114    * download the [[http://www.generalinterface.org/|General Interface 3.9.1]] Debug edition (in a production environment use the Standard edition) and place the content of the archive into the {{{path-to-ISOcat/develop/mod-gi/gi/3.9.1/}}} directory
     114   * download the [[http://www.generalinterface.org/|General Interface 3.9.1]] Debug edition (in a production environment use the Standard edition) and place the content of the archive into the {{{path-to-ISOcat/develop/mod-gi/gi/3_9_1/}}} directory (notice the underscores)
    115115   * download the [[http://tango.freedesktop.org/Tango_Icon_Library|Tango icon library]] {{{tango-icon-theme}}} and place the content of the archive into the {{{path-to-ISOcat/develop/mod-Tango/Tango/}}} directory (in a production environment ISOcat only needs the {{{16x16}}} subdirectory)
    116116   * download the [[http://www.famfamfam.com/lab/icons/silk/|famfamfam silk icon library]] and place the content of the archive into the {{{path-to-ISOcat/develop/mod-famfamfam/famfamfam/silk}}} directory
     
    205205 * goto the ''ISOcat system management'' in the ''applications''
    206206 * enter a valid SMTP server in the ''Configure'' form
     207 * goto [[http://localhost:8080/isocat/]]
    207208
    208209'''Note''':  There is currently a concurrency problem in the class loader which can lead to multiple Saxon Configuations, which should be a Singleton. Check for any 'Externally supplied NodeInfo belongs to the wrong Configuration' messages during startup or a first access. If this happens restart the server and check again ... the concurrency bug doesn't happen that often.