Comments:JAMWiki 0.6.6

[Edit]JAMWiki 0.6.6

Archived from the Feedback page:

[Edit]Current Release Status

The next release is still in heavy development, but the code seems stable enough that I've copied the latest to jamwiki.org for further exposure. The major focus of development thus far has been simplifying and cleaning up the parser code while trying to improve Mediawiki compatibility. Since the parser is a core piece of JAMWiki code it is expected that there will be some bugs, and since upgrading jamwiki.org I've already discovered a problem with section edits and with comments (both fixed). Additionally I'm seeing some odd corner cases where paragraphs aren't parsed correctly. All regresssions and issues should get fixed before the final 0.6.6 release, and any reports of strange rendering on jamwiki.org would help in tracking down problems.

It will probably take a while for the code to settle down enough for a beta to be practical, but in the mean time anyone interested in running bleeding-edge code can build it from source. As always, feedback is appreciated. -- Ryan 03-Apr-2008 22:55 PDT

[Edit]JAMWiki 0.6.6 beta 1

The next release is pretty close to being ready, so here's the first beta for testing.

Notable changes in this release include:

  • Major parser updates. The CHANGELOG has complete details, but output should more exactly match Mediawiki, and some additional Mediawiki syntax is now supported.
  • Implementation of Spring managed transactions for the database from User:dallas.
  • An admin setting to allow resetting user passwords.
  • Much, much more.

Testing and feedback is appreciated. There are a couple of minor bugs I'd like to address before the final release, but the current plan is to release a final version in the next couple of weeks. -- Ryan 11-May-2008 19:39 PDT

The WAR file link has now been fixed. I'll update my build scripts to make sure that the file name is correct in the future. -- Ryan 16-May-2008 08:00 PDT

[Edit]JAMWiki 0.6.6 beta 2

Here's a second beta for JAMWiki 0.6.6:

Notable changes in this release include:

  • Workaround for the annoying "user is null" bug when restarting the server with a "remember me" cookie set.
  • Fix for a parser issue that could result in IllegalStateExceptions for certain wiki content.
  • Updated translations.
  • Upgrade to the latest version of Spring and Spring (Acegi) Security.

I'll be going out of town for several weeks starting in early June, so my hope is that it will be possible to release the final JAMWiki 0.6.6 in the next week. If there are serious bugs found, or if not enough testing can be done, then the next release will unfortunately probably slip until after I return in July. -- Ryan 26-May-2008 19:13 PDT

JAMWiki 0.6.6 beta 2 breaks installation with MySQL on my local environment, so that issue will need to be fixed before a final release is possible. -- Ryan 28-May-2008 22:04 PDT
This issue may have just been due to some changes in my local environment, but revision 2231 resolves the problem and should make the JDBC driver loading code a bit more robust. -- Ryan 01-Jun-2008 10:03 PDT

[Edit]Migrating from HSQL to MySQL||PostgreSQL||insert your favorite database backend

Archived from the Feedback page:

I searched. I looked around. Nothing discussed that stood out as "what I'm trying to do..." So, I've been toying around with JAMWiki (v0.6.5) for about a month on my laptop running it "out of the box" with HSQL. I have liked JAMWiki so much I started using it to store data that is intended for production. How do I dump my HSQL data so to feed it back to a production database like PostgreSQL or MySQL?

I did a few quick internet searches to see if there was an easy way to export data from HSQL, but didn't have much luck finding anything. Since a number of people have asked for this functionality it is probably something that needs to be done soon, so would it be useful to have the data in some sort of XML dump? It would then be up to you to import that file into a database, but I suspect that most databases support XML import these days. Note that this would not be the full XML import/export that people have asked about, but simply a rough "dump everything to an XML file on the filesystem" sort of tool. If that would be useful let me know and I can try to throw something together this week. Alternatively, if there is another suggestion that can be done I'd be interested in hearing ideas. -- Ryan 29-Mar-2008 20:26 PDT
I think useful. Most definitely a start. Thank you Ryan! The OpenOffice site had some hints about exporting HSQL to CSV that might be helpful, here and here.
I missed the second link while search yesterday - that one should be extremely easy to put in place. Let me see what I can do. -- Ryan 30-Mar-2008 09:26 PDT
revision 2134 is a first attempt at adding this functionality. It needs a bit more work to fix a corner-case where data could be incorrectly appended to the CSV file, but hopefully it should be sufficient for most users. Feedback is appreciated - I'll try to roll a beta of the 0.6.6 version (including this change) within the next few weeks. -- Ryan 30-Mar-2008 13:42 PDT
revision 2141 should resolve the issue with multiple exports appending to the CSV files instead of ovwriting them. The only remaining issue I'm aware of is that exporting non-ASCII characters seems to convert everything to ASCII. I've set the textdb.encoding property using several different approaches with no luck, so I'm not sure if this is an HSQL issue, an issue specific to my laptop setup, or some other problem. For now I'll leave it to some other interested person to investigate and (hopefully) resolve, although if enough people find it to be a major problem then I'll revisit it. -- Ryan 31-Mar-2008 22:40 PDT
I also had a need to migrate from the initial internal HSQL database to a production database. In order to make this as easy as possible, I wrote a new Admin-only function Migrate Wiki to New Database accessed via the "Special:Maintenance" page. This option creates the JAMWiki database tables in the new database, copies across the table contents from the old database into the new database, and then updates the configuration to point to the new database. It needs to be tested with more databases (I used it to go from HSQLDB to Sybase ASA and back), but I think it should work for all of the databases supported by JAMWiki. I've added some documentation for this to Migrate Wiki to new Database, checked in as revision 2168 -- Dallas 12-Apr-2008 10:01 PDT