It is possible to execute Java method with current realization of the General Service Task. But there are still many limitations:

• It is not possible to send data to the java method you're invoking
• It is not possible to receive data from the java method you invoked
• It is possible to chose Web Service to call in General Service Task, but it is not possible to use it at runtime.
• If you have properly configured Service Task in the old designer, all listed below properties will be lost and it won't be possible to use Service Task at runtime after migration).

Missing Critical properties:

• Process itself has no way to set up Imports property to define Web Service to call ( TODO: Move this to a new ticket )

Other missing properties:

• Missing data assignments property
• Missing Ad-Hoc autostart property
• Missing IsAsync property
• Missing Multiple Instance property
• Missing On Entry Actions property (with script language property)
• Missing On Exit Actions property (with script language property)
• Missing SLA Due Date property (covered by JBPM-8615)

Next improvements:

• Data assignemnts - we can consider to drop it if Parameter and Result are the only properties we need for the Service Task execution)
  • For both Java and Web Service - Parameter property (to send data to the java method or web service)
  • For both Java and Web Service - Result property (to receive data from java method or web service)