Dave McKain
Dave McKain
The rendering for textEntryInteraction and extendedTextInteraction is currently ignoring any response default values. (This is a regression introduced while trying to make these interactions handle bad/invalid responses better.)
The XML parsing code currently rejects schema locations that are not explicitly supported either natively, or by a registered extension. This doesn't play nicely if the XML explicitly declares any...
The server logs show a NullPointerException in SingleValueAttribute.parseDomAttributeValue(). This could happen if baseType is null. There seems to be some odd mutation of baseTypes happening in LookupTable. I suspect this...
The rendering XSLT for `printedVariable` is currently expecting `@index` to be an integer, rather than `integerOrVariableRef`, and is consequently blowing up if the attribute is a variable reference.
RuntimeExceptions thrown during assessment rendering should probably set the 'exploded' flag on the CandidateSession, as there's nothing the candidate can do to fix things at this point and the candidate...
The implementation of `printedVariable` is delegating to Java's String formatting classes, which does not support of all of the specified formats. The rendering XSLT is falling over when it encounters...
The 'view' attribute (e.g. rubricBlock) has never been used in the rendering as far as I can tell. This probably needs added in.
The QTI specification doesn't mention what should happen if multiple interactions are bound to the same response variable. For example: ``` xml ... ``` Currently JQTI+ is not testing for...
Sue Milne has requested the ability for candidates to download the final feedback for a test in certain circumstances.
The information model for prompt says that it must contain inlineStatics. However the (final version of the) schema appears to have a more relaxed content model. I will need to...