Ampersand in workflow specification description crashes resource service

[mlawry]

Hi,

I created a "loan process.yawl" file loan process.zip and typed into the Description field under Specification "Hello & world". I then tried to upload this file to YAWL Resource Service (Cases tab) and I get an exception.

Before you try to do this, please note that I was not able to access the Cases tab of Resource Service afterwards. I had to delete the YAWL database and start from scratch again because every time I click on the Cases tab, I get that same exception. So you may want to try this on a brand new YAWL installation rather than an existing installation.

The problem seems to be the ampersand in the description was not converted into an XML entity. Exception message from catalina.out is:

2017-01-12 04:58:02,729 [ERROR] JDOMUtil             :- JDOMException converting to Document, String = <response><specificationData><uri>loan_process</uri><id>UID_86ff3eb2-c61d-4767-ba6f-9e153184e3e8</id><documentation>Hello & world.</documentation><rootNetID>Net</rootNetID><version>3.0</version><specversion>1.0</specversion><status>loaded</status><metaTitle/><authors><author>lyao</author></authors></specificationData></response>
org.jdom2.input.JDOMParseException: Error on line 1: The entity name must immediately follow the '&' in the entity reference.

[yawlfoundation]

Fixed in latest update (yawl build 1435). The problem occurred in the method that creates a specification summary for the specifications list.