Paul Boone

Quick Tutorial: Bundling a merb application to a .war

Paul Boone — Tue, 20 May 2008 03:55:10 +0000

Make sure you have the JRuby warbler gem installed.
Create a warble config file from the root directory of your merb application. The command should look something like this: jruby -S warble config. The file will be placed at config/warble.rb.
Edit line 55 of warble.rb to read: config.webxml.booter = :merb
Edit line 33 of warble.rb to read: config.gems = ["merb-core","merb-more"]. Add other required gems, if necessary.
At the root directory of your web application, run: jruby -S warble.
Deploy the war.

Using Logging and Test::Unit together

Paul Boone — Fri, 02 May 2008 19:18:00 +0000

If you use Tim Pease’s ruby Logging library in conjunction with Test::Unit, you must make sure to require ‘logging’ before you require ‘test/unit’. Both Logging and Test::Unit make use of Ruby’s at_exit method hook: Logging uses it to close any appenders (e.g. if you are writing a log to a file, it closes the file), and Test::Unit uses it to actually run the unit tests. Ruby executes any at_exit methods in reverse order, so if you require ‘logging’ after you require ‘test/unit’ then your logs are closed before the unit tests are run. If you try to log anything in the code you are testing, you’ll get an error like this:

  1) Error:
test_at_exit_conflict(AtExitConflictTest):
RuntimeError: appender '' is closed
method append in appender.rb at line 107
method log_event in logger.rb at line 366
method each in logger.rb at line 366
method log_event in logger.rb at line 366
method debug in (eval) at line 6
method test_at_exit_conflict in logging-testunit-atexit.rb at line 11

This code will throw the above exception:

require "test/unit"
require "logging"

$log = Logging::Logger["testlogger"]
$log.add_appenders(Logging::Appender.stdout)

class AtExitConflictTest < Test::Unit::TestCase
  def test_at_exit_conflict
    $log.debug("test")
    assert(true)
  end
end

Reverse the order of the require ‘test/unit’ and require ‘logging’ to solve the problem.

OpenCms 7 XStandard WYSIWYG Module v0.6

Paul Boone — Wed, 16 Apr 2008 19:09:26 +0000

This is an initial release of an XStandard WYSIWYG Module for OpenCms 7+. From the XStandard website:

XStandard is the leading standards-compliant plug-in WYSIWYG editor for desktop applications and browser-based content management systems (IE/Firefox/Safari/Opera). The editor generates clean XHTML Strict or 1.1, and uses CSS for formatting, to ensure the clean separation of content from presentation. The editor is keyboard accessible, and markup generated by XStandard meets the most demanding accessibility requirements.

You should use the XStandard editor instead of the FCKEditor that comes with OpenCms if you want your application to generate well-formed, accessible, and standards-compliant XHTML. In some cases, such as for any public website of a federal agency of the USA, this is legally required.

Features

XStandard 2.0 integration into OpenCms workspace
Integration with OpenCms image, download, link galleries.

Notably missing from this release:

Integration with XStandard’s web service plugins: spell checker, image gallery, file gallery, etc.
Localization.
Integration with OpenCms’s WYSIWYG button customization and permissions system.

Requirements and Installation

This module requires a full version of XStandard Pro, not the lite version. You can get a trial pro license from XStandard. Tested with Opencms 7.0.3 / 7.0.4. May or may not work with other versions.

To install:

Install XStandard–see http://xstandard.com/
Import the com.mindbucket.editors.xstandard.zip module into the OpenCms workplace.
Copy the XStandard license.txt file provided to you by http://xstandard.com/ to /system/workplace/editors/xstandard/license.txt in your OpenCms vfs.
Optionally, modify /system/workplace/editors/xstandard/editor.jsp with any additional parameters you want to use with your embedded XStandard Editor.
Copy the com.mindbucket.editors.xstandard.jar into your OpenCms instance’s lib directory.
Restart OpenCms.
In OpenCms, go to Preferences -> Editors and you should have an “XStandard” editor available under “Page with free text”.

Download OpenCms 7 XStandard WYSIWYG Module v0.6.