This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 . It is not the current version, and thus it cannot be edited.

Back to current version Restore this version

FAQ#

This Page is supposed to help you getting started with the development of KnowWE. Feel free to add your Solutions to this page. If you don't find the Informations you need here, you can post it in the Forum.

What is a Plugin?#

A Plugin is a module extending KnowWE's functionality. A plugin needs a plugin.xml file defining the Extensions for this plugin.

What is an Extension?#

An Extension implements the plugin's functionality using an Extension Point. For further definition and usage instructions see this page..

What is an Extension Point?#

An Extension Point has a specific type, for example Action, TagHandler, TypeHandler or EventListener. The defined extension point specifies that each extension has to give values for class, name, description, version, and priority. This has to be defined by each extension point; an extension point further can require additional value, for example the specification of a file name. For further definition and usage instructions see this page.

What is the Scope of an extension?#

A scope is an selector of a specific subset of KDOM nodes. Its selection is based on the type of the KDOM nodes itself as well as on the type of the KDOM node's anchestors. It can be compared a little bit to the css selectors.

The scope is a path of those KDOM node types that should be matched/selected. The path can be relative (anywhere in the KDOM tree) or root based. Specific path wildcards as "*" and "**" are allowed. The different kinds of Scopes and their usage are explained here.

Creating new projects#

Every new project has to be allocated to one of the three main repositories: d3web-core, d3web-KnowWE or Research.

Creating the project in Eclipse#

• Do a right click on the main project (one of the three projects mentioned above) → New → Other…. In the window, in the Maven folder, select "Maven Module"
• Check the checkbox called "Skip Archetype selection", give the project a name and hit Next.
• Enter a human-readable name into the field "Name", fill in "Description" as needed.
• Click "Finish".

Now you will see the new project in the Eclipse Project Explorer. Now you can start creating or copying source files. Using the UTF-8 encoding is mandatory.

License header#

Every .java file must contain the license header, starting in the first line. Be sure to have an empty line between the license and the package declaration.

The license is to look like this:

/*
 * Copyright (C) 2010 Chair of Artificial Intelligence and Applied Informatics
 *                    Computer Science VI, University of Wuerzburg
 *
 * This is free software; you can redistribute it and/or modify it
 * under the terms of the GNU Lesser General Public License as
 * published by the Free Software Foundation; either version 3 of
 * the License, or (at your option) any later version.
 *
 * This software is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
 * Lesser General Public License for more details.
 *
 * You should have received a copy of the GNU Lesser General Public
 * License along with this software; if not, write to the Free
 * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
 * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
 */
 

You can do this automatically by adding codetemplates.xml in Eclipse: Window -> Preferences -> Java -> Code Style -> Code Templates

First check-in#

You have to perform the first check-in using the chosen main repository (c.f. above).

• Right click the main project → Team → Commit.
• Now exclude the folders target/ and .settings/! (Uncheck the check boxes)
• Enter your commit message → Commit.

Now you can enable SVN access directly for your newly created project: Perform a right click on the new project → Team → Share. Select SVN, you will find the repository location already set up. Hit Finish.

To complete the process, you have to ignore target/ and .settings permanently. Select both folders in the Project Explorer with Ctrl/Command, right click → Team → Add to svn:ignore. Click OK in the window that opens.

Finally, commit the ignore settings: right click → Team → Commit. Done.

Why isn't Plugin X included in my Build?#

You need to enable the plug-ins you want to build into KnowWE when using Eclipse. Here's how:

Open your Run Configuration for the KnowWE build and add parameters for the plug-ins you want to have in the goals section.

For instance: You want to enable the Comment plug-in. Here, you have to add a comment-plugin parameter. List all the profile names for the Plug-ins you want to add in the Profiles Section and build KnowWE.

See the screenshot on the right for another example.

Why does Eclipse not catch breakpoints?#

This Issue is caused by an outdated JDK. Please update your JDK to the latest Version.

Why do i get a java.util.MissingResourceException: Can't find bundle for base name Exception?#

This happens after cleaning the workspace.

Solution: For each of the two maven super projects (d3web, d3web-KnowWE), select the project, right click on it, "Run as...", "Maven package".

What do I need to do after I change a .java file?#

Usually you only have to refresh your browser page. Hot Code Replacement makes your changes effective at runtime.

I'm done editing. How to make my changes permanent?#

You don't have to worry that you changes will be lost after you shut down KnowWE. To make the changes effective for the next restart, you have to perform Maven Install on KnowWE-App.

Hot Code Replacement failed. What to do?#

Sometimes, especially when doing major changes to a .java file, Hot Code Replacement fails. In this case you have to

• Quit Tomcat
• Perform a Maven Install on KnowWE-App and
• Start Tomcat again.

What do I need to do after I change a Non-Java file?#

Unfortunately, there is no Hot Code Replacement for Non-Java files. However, there is a How-To for developing Javascript at runtime, which may be useful for you.

How to make changes to Non-Java files effective:

• Quit Tomcat
• Perform Maven Install on your plugin aswell as KnowWE-App
• Restart Tomcat

Tomcat successfully starts, but the wiki pages are not loaded. What to do?#

This can happen when you perform a Maven Install while Tomcat is still running. To fix this, you have to follow these steps:

• Right click on KnowWE-App in Eclipse and select

Tomcat > Update Tomcat Context

• Start Tomcat

Offline Build (if Artifactory is not available or you have no Internet connection)#

Create a second runtime configuration for building KnowWE, just like shown here: http://d3webwiki.informatik.uni-wuerzburg.de/Wiki.jsp?page=Workspace#section-Workspace-CreateARunConfigurationForBuildingTheWiki, just check the "Offline" checkbox. Note: Do not enable this option for your regular build, only use it if Artifactory is down or you are not connected to the internet!

Why are Umlauts viewed uncorrectly?#

Tomcat can be configured in UTF-8 to handle Umlauts correctlty. Look at http://www.jspwiki.org/wiki/BugProblemsWithGermanUmlaute //End Old

What... ? and Why...? Questions
Coordinate with How-To