Active development of JAMWiki has ceased, and bug fixes and support will be limited at best. If you are interested in taking over management of JAMWiki please send an email to the jamwiki-devel mailing list.

User comments:RegisDecamps


Sourceforge ID

Please let me know what your Sourceforge login is if you'd like write access to Subversion. Unit tests and small fixes can be committed directly to the trunk, but it would be good to get a bit more discussion before any major changes (such as Tech:Maven) are put on the trunk - if you'd like to start working on that now it would be better to just create a branch in Subversion. Thanks for taking the time to write up the Maven proposal! -- Ryan 11-Jul-2007 12:08 PDT

Thanks & a request

Thanks for all of your work on the Tech:Maven page and Building from Source. One request, however, is that rather than removing old discussions from the comments pages it would be better to leave them or else archive the discussion if the page gets too long (for example in Comments:Building from Source/Archive). The benefit is that if someone comes along in the future and is trying to see the process that was followed to get to a certain result it will all be available & easy to follow. It's not a big issue, but it's inevitable that someone will come along in the future and ask "why did you do it this way", and it's easier for someone who is lazy (like myself!) to just point them to the full discussion rather than trying to explain. Thanks again - it's only 1:45 PM here in Los Angeles and already it looks like a lot has been accomplished. -- Ryan 22-Jul-2007 13:21 PDT

OK, I'll try not to remove potentially useful things in the future, even though I personnaly tend to prefer concice and clean articles.
I agree that the articles should definitely be clean, and you've done a good job with cleaning up some of the existing article pages. Comments pages are by nature going to be a bit messy, so if necessary we can clean them up by moving old conversations to archive pages, but it would be best if the conversations are still available somewhere for people to read without the need to browse article history - see wikipedia:Wikipedia:Talk page guidelines for Wikipedia's policy, which I think is a good one. -- Ryan 24-Jul-2007 09:04 PDT

Thanks a lot for refactoring the CheckboxTag & RadioTag classes! I'm a big fan of commits like that one that get rid of 200+ lines of code! -- Ryan 23-Jul-2007 21:39 PDT

You can thank the PMD plugin, indeed ;-) Regis Decamps 24-Jul-2007 02:30 PDT


Although I haven't been keeping a close watch on the parser isolation changes I have looked over a few of the commits, and in addition to the parser work it looks like you've made a lot of code cleanups in that branch, such as revision 1729. If you'd like to please feel free to immediately merge minor cleanups onto trunk - simple cleanups are always welcome. And thanks again for all of the work you've been doing lately! -- Ryan 02-Aug-2007 23:34 PDT

Parser Isolation

isolate parser from jamwiki core. I think I'll give up. It seems everything is intercoupled.

The inter-coupling is an issue, and I'm not sure how best to resolve it at this time. Since this change won't be completed for 0.6.1, should the jamwiki-core and jamwiki-parser-jflex projects be kept, or would it make more sense to remove them for now? -- Ryan 30-Sep-2007 08:52 PDT


Hi Regis, Ryan pointed me to you. I have succesfully installed jamwiki in eclipse/wtp but I suffer from a severe problem. When I change some java source or a properties file the context gets realoaded in order to load the new classes. Since then the internal DB remains locked with

26.11.2007 00:22:56 org.apache.catalina.core.StandardContext reload
INFO: Reloading this Context has started
log4j:WARN No appenders could be found for logger (org.apache.commons.digester.Digester.sax).
log4j:WARN Please initialize the log4j system properly.
26.11.2007 00:23:00 org.jamwiki.utils.WikiLogger severe
SCHWERWIEGEND: Unable to retrieve default roles for GROUP_ANONYMOUS
java.sql.SQLException: The database is already in use by another process: org.hsqldb.persist.NIOLockFile@3dbb2eaf[file =D:\wiki-test\database\jamwiki.lck, exists=true, locked=false, valid=false, fl =null]: java.lang.Exception: Der Prozess kann nicht auf die Datei zugreifen, da ein anderer Prozess einen Teil der Datei gesperrt hat : D:\wiki-test\database\jamwiki.lck
	at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
	at org.hsqldb.jdbc.jdbcConnection.<init>(Unknown Source)
	at org.hsqldb.jdbcDriver.getConnection(Unknown Source)
	at org.hsqldb.jdbcDriver.connect(Unknown Source)
	at java.sql.DriverManager.getConnection(Unknown Source)
	at java.sql.DriverManager.getConnection(Unknown Source)
	at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(
	at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(
	at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(
	at org.apache.commons.dbcp.PoolingDriver.connect(
	at java.sql.DriverManager.getConnection(Unknown Source)
	at java.sql.DriverManager.getConnection(Unknown Source)
	at org.jamwiki.db.DatabaseConnection.setUpConnectionPool(
	at org.jamwiki.db.DatabaseConnection.getConnection(
	at org.jamwiki.db.WikiPreparedStatement.executeQuery(
	at org.jamwiki.db.AnsiQueryHandler.getRoleMapGroup(
	at org.jamwiki.db.AnsiDataHandler.getRoleMapGroup(
	at org.jamwiki.authentication.JAMWikiAnonymousProcessingFilter.initRoles(
	at org.jamwiki.authentication.JAMWikiAnonymousProcessingFilter.afterPropertiesSet(
	at org.springframework.web.context.ContextLoader.createWebApplicationContext(
	at org.springframework.web.context.ContextLoader.initWebApplicationContext(
	at org.springframework.web.context.ContextLoaderListener.contextInitialized(
	at org.apache.catalina.core.StandardContext.listenerStart(
	at org.apache.catalina.core.StandardContext.start(
	at org.apache.catalina.core.StandardContext.reload(
	at org.apache.catalina.loader.WebappLoader.backgroundProcess(
	at org.apache.catalina.core.ContainerBase.backgroundProcess(
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(
	at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(
	at org.apache.catalina.core.ContainerBase$
	at Source)
Exception in thread "HSQLDB Timer @174d93a" java.lang.NullPointerException
	at org.hsqldb.lib.HsqlTimer.nextTask(Unknown Source)
	at org.hsqldb.lib.HsqlTimer$ Source)
	at Source)

jamwiki goes bezerk. The only solution is to restart tomcat from within WTP. How can I resolve this issue with eclise/wtp? It seems like jamwiki does not release the lock on the internal DB file when the context is shutdown.
I really want to get this run and commit a lot of features.
thx --Michael-O 25-Nov-2007 15:14 PST