selection of "spring" resolver for global results validation error

[zhouyixiang]

jBPM document says:

Last but not least, there is Spring based resolver available as well that allows to simply look up a bean by its identifier from spring application context. This resolver is not used in Business Central (kie-workbench) as it does not use spring but whenever jBPM is used together with Spring it might become handy when deploying kjars into the runtime.

And, there's 'spring' in the options of resolver for globals:

However, if I click 'Build' button this will fail and an error message will be shown as:

Not valid resolver selected for kycServiceImpl

By checking the response of the ajax call for 'Build', it looks like the error was triggered by the validation logic here. If I change the resolver to MVEL and supply right MVEL expression the build will pass. The validation logic only allows "reflection" and "mvel". I'm not sure if this is the reason why build failed. If it is, will we have a fix on this? Please forgive me if I reported this issue at a wrong place (I'm new to jBPM).

I used the jBPM standalone distribution "jbpm-server-7.33.0.Final-dist".

[karlnicholas]

Me 2