Changes between Version 9 and Version 10 of DocumentationForDeveloping


Ignore:
Timestamp:
11/30/09 10:38:49 (8 years ago)
Author:
kiesel
Comment:

Update, better configuration notes

Legend:

Unmodified
Added
Removed
Modified
  • DocumentationForDeveloping

    v9 v10  
     1[[PageOutline]] 
    12= Development Setup = 
    2  
    3 '''NOTE:''' Kaukolu has been ported to WTP in the beginning of 2007. Read more concerning changes on WebToolsPlatformNotes. 
    43 
    54== Setting Everything Up == 
    65 
    76Requirements: 
    8  * '''Eclipse Web Tools Platform''' plugin set. WTP is available on Eclipse's Callisto Discovery Site (assuming Eclipse 3.2 or higher) but of course you can also install it manually. 
    9  * '''AJDT''' (http://www.eclipse.org/ajdt/) has to be installed. 
     7 * '''Eclipse Web Tools Platform''' plugin set. WTP is included in recent Eclipse for Java EE builds. 
     8 * '''AJDT''' (http://www.eclipse.org/ajdt/) might be necessary. 
    109 
    11 Build Kaukolu (see below). 
     10Build Kaukolu (see below). For configuration: 
     11 * Add attribute {{{URIEncoding="UTF-8"}}} to the appropriate connector section in Tomcat's server.xml - otherwise non-ASCII characters in page names will break. 
     12 * Configure Kaukolu/JSPWiki. Either: 
     13   * Edit jspwiki.properties. All paths (search for {{{data/}}}) and {{{baseURL}}} need to be adjusted. 
     14   * Go to http://localhost:8080/kaukolu/Install.jsp for configuration. An admin account will get created then, too. The Kaukolu installation script is not well tested though. 
     15 * Go to http://localhost:8080/kaukolu . 
    1216 
    13 Add attribute {{{URIEncoding="UTF-8"}}} to the appropriate connector section in Tomcat's server.xml - otherwise non-ASCII characters in page names will break. 
    14  
    15 Go to http://localhost:8080/kaukolu . This launches Kaukolu in default configuration - data will be saved in webapps folder, no admin. 
    16 If you want Kaukolu to save its data somewhere else, install it properly by going to http://localhost:8080/kaukolu/Install.jsp . An admin account will get created then, too. 
    17  
    18 === Building === 
     17== Building == 
    1918 
    2019Hint (for DFKI-KM): To install a readily configured Eclipse, just follow the instructions on http://wiki.km.opendfki.de/wiki/HowToEclipseSchnellInstallation 
     
    2928Hint: By connecting a servlet container runtime to the Kaukolu project, deployment can be managed through the "Server" view in the "J2EE" perspective. 
    3029 
    31 '''1) Installing a Tomcat runtime for the default config''' 
     30=== 1) Installing a Tomcat runtime for the default config === 
    3231 
    3332If you haven't already set up a server runtime in Eclipse, do so by visiting 'Window --> Perferences --> Servers --> Installed Runtimes' and click "Add". Follow the instructions on the screen to create a new Tomcat 5.5 server runtime definition. The server has to be named "Tomcat 5.5 Default Runtime". The next step is to connect the newly defined runtime to the Kaukolu server project. Do so by opening the "Servers" view and create a new server instance by right-click --> "New" --> "Server" --> "Apache Tomcat v5.5 Server" --> "Finish". Then add the kaukolu project to the server by right-clicking on the newly created server --> "Add and remove projects". Now, add the kaukolu project. 
    3433 
    35 '''2) Installing an all different server runtime''' 
     34=== 2) Installing an all different server runtime === 
    3635 
    3736You may also decide to run Kaukolu in a servlet container or application server other than Tomcat. This means however, that you have to create an all new server project and modify the Kaukolu project to link to that new server configuration. 
     
    8685'''UPDATE:''' I discussed this issue on the WTP mailing list, and I found a partial solution which at least lets you finally debug JSPs and custom tag implementations. The problem for me was that a) simply setting breakpoints in a JSP and starting the server does not work and b) explicitly saying "Debug on server" in a JSPs context menu threw an error at me indicating that "the current selection is not within a valid module". As I have learned on the mailing list, this error message means that WTP can't associate the JSP with a web module as connected to a Server project. This is a bug (which also happens in other circumstances), but there is a workaround to still be able to debug the JSP: Instead of selecting "debug on server" select "debug ..." and manually select the run config. Now all breakpoints will be correctly reached. 
    8786I was told that the "not within a valid module" bug only appears when selecting "debug on server" through the editor context menu. It should work however when doing the same through the navigator on the left hand side of the workbench. 
     87 
     88== History == 
     89 * Kaukolu has been ported to WTP in the beginning of 2007. Read more concerning changes on WebToolsPlatformNotes.