Dave McKain

(Would also be worth checking the handling of CandidateExceptions on state changing candidate service calls to make sure all of this joins up correctly.)

Fixed in commit 2e8d9ab.

I did have a brief look a while ago but it didn't seem that easy to do. I'll have to check again. In the mean time, the artifacts are being...

Hi there! That does sound like a useful feature to have, and hopefully shouldn't be too difficult to implement. If you're willing to have a go at implementing this then...

Hi Rosemary. My memory of the QTI 2.1 spec is getting a bit hazy now...! But I think that QTIWorks _is_ doing the right thing here. `correctResponse` is used to...

`correctResponse` allows 1..* `value`s so that you can specify a correct response having container (e.g. multiple) cardinality, not to allow you to specify multiple different correct responses. For example, in...

As of 1.0-beta8 or 1.0.0, the rendering XSLT should no longer blow up when encountering an unsupported format.

Summary of current implementation... The current implementation of printedVariable simply passes the variable to Java's implementation of 'formatted print' (printf) using the computed value of the variable. This therefore doesn't...

See also issue #57.

I've added a helper to clear up any application-created `ThreadLocal`s, which is a common cause of these types of memory leaks. This hasn't fixed this particular issue.