Description of problem: when deploying a kjar over REST the 'strategy' parameter is ignored, and the default value 'SINGLETON' is used, even if e.g. 'PER_PROCESS_INSTANCE' is specified as request parameter.

This seems to be a regression from 6.0.1.ER1 to 6.0.1.ER2

Version-Release number of selected component (if applicable): 6.0.1.ER2

How reproducible: Consistently

Steps to Reproduce:
Against a running instance of BPMS 6.0.1.ER2, issue the following commands:
curl -X POST -HAccept:application/json --user admin1:admin -d "strategy=PER_PROCESS_INSTANCE" http://127.0.0.1:8080/business-central/rest/deployment/org.jboss.btison.bpms.testbed.datamodel-version:kjar:0.0.1/deploy

curl -X GET -HAccept:application/json --user admin1:admin http://127.0.0.1:8080/business-central/rest/deployment/org.jboss.btison.bpms.testbed.datamodel-version:kjar:0.0.1

(replace admin/admin1 and the deployment id with appropriate values)

Actual results:

{
"groupId": "org.jboss.btison.bpms.testbed.datamodel-version",
"artifactId": "kjar",
"version": "0.0.1",
"kbaseName": null,
"ksessionName": null,
"strategy": "SINGLETON",
"identifier": "org.jboss.btison.bpms.testbed.datamodel-version:kjar:0.0.1",
"status": "DEPLOYED"
}

Expected results:
{
"groupId": "org.jboss.btison.bpms.testbed.datamodel-version",
"artifactId": "kjar",
"version": "0.0.1",
"kbaseName": "",
"ksessionName": "",
"strategy": "PER_PROCESS_INSTANCE",
"identifier": "org.jboss.btison.bpms.testbed.datamodel-version:kjar:0.0.1",
"status": "DEPLOYED"
}

Additional info: