This page (revision-90) was last changed on 24-Feb-2016 11:06 by Albrecht Striffler

This page was created on 20-Nov-2012 15:45 by UnknownAuthor

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
90 24-Feb-2016 11:06 9 KB Albrecht Striffler to previous
89 15-May-2014 09:33 9 KB Volker Belli to previous | to last
88 15-May-2014 09:32 9 KB Volker Belli to previous | to last
87 15-May-2014 09:30 9 KB Volker Belli to previous | to last
86 21-Jun-2013 15:09 8 KB Jochen Reutelshöfer to previous | to last
85 21-Jun-2013 15:08 8 KB Jochen Reutelshöfer to previous | to last
84 21-Dec-2012 16:15 7 KB Jochen Reutelshöfer to previous | to last
83 21-Dec-2012 16:14 7 KB Jochen Reutelshöfer to previous | to last
82 18-Dec-2012 17:47 7 KB Alex Legler to previous | to last Fix Image link URL
81 17-Dec-2012 21:33 7 KB CarstenWasner to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 4 added 2 lines
At line 7 added 2 lines
At line 10 added one line
At line 13 added one line
At line 15 added one line
At line 18 added one line
At line 20 added one line
At line 25 added one line
At line 27 added one line
At line 20 removed 2 lines
! Why cannot my JUnit tests be executed?
If the message appears 'dependencies/output.txt not found' read further in this [howto|How-To Initialize Plugin Manager for JUnit Tests].
At line 33 added 2 lines
At line 36 added one line
At line 47 added one line
At line 49 added one line
At line 53 added one line
At line 76 added one line
At line 79 added one line
At line 82 added one line
At line 98 added one line
At line 100 added one line
At line 105 added one line
At line 108 added one line
At line 110 added one line
At line 118 added one line
At line 126 added one line
At line 128 added one line
At line 131 added one line
At line 133 added one line
At line 136 added 6 lines
! Why cannot my JUnit tests be executed?
If the message appears 'dependencies/output.txt not found' read further in this [howto|How-To Initialize Plugin Manager for JUnit Tests].
At line 143 added 2 lines
At line 147 added one line
At line 149 added 2 lines
At line 152 added one line
At line 155 added one line
At line 116 removed one line
This issue is caused by an outdated JDK. Please update your JDK to the [latest version of Java 6 | http://www.oracle.com/technetwork/java/javaee/downloads/index.html].
At line 158 added 3 lines
This issue is caused by an outdated JDK. Please update your JDK to the [latest version | http://www.oracle.com/technetwork/java/javaee/downloads/index.html].
At line 162 added one line
At line 167 added 21 lines
! INFO: ERROR: Failed to create a Wiki engine: JSPWiki: Unable to load and setup properties from jspwiki.properties.
This is a missleading message display caused by unprecise error handling within jspwiki initialization code. The try-catch does not only include reading of the jspwiki.properties file, but also initialization of plugins/filters, i.e. also entire initialisiation of KnowWE. If you have recently changed code of KnowWE or a KnowWE-Plugin this error __most likely__ has __nothing__ to do with the jspwiki.properties file. It can be any kind of exception happening during KnowWE initialization. After the ''Unable to load and setup properties from jspwiki.properties'' the ''e.getMessage()'' of the actual exception is shown (without stack-trace unfortunately). __Tipp:__ Check the message string to guess what kind of exception it might have been; Consider your latest code changes; if nothing helps start debugging, e.g. in ''Environment.initInstance()''
! Are d3web's Session objects thread-safe for multi-threaded environments?
In general a single d3web session is not thread-safe for write access. Reading contents from the same session with multiple threads is ok. But having an applications where multiple threads simultaneously read/write to a session, they need to be synchronized. Even if there is only one thread that writes to the session, it need to be synchronized with all reading threads. By convention, in d3web this should be done using the "Session"-Object as the semaphore for synchronization. This makes sure that your code will be interoperable with all other applications code (also considering this convention), without being in danger to create deadlocks.
%%prettify
{{{
// put your non d3web-code here
// ...
synchronized (session) {
// your read/write access to the session or blackboard or ... here
// ...
}
}}}
/%