Description
-
-
- Problem description
-
The name of the camunda task bean is `camunda.taskForm`. When the bean is used in combination with apache myfaces and apache EL, the bean cannot be used since these implementations interpret the dot in `camunda.taskForm` as name seperator and attempt to resolve a bean named "camunda" having a property named `taskForm`.
This affects IBM Websphere users as well.
-
-
- Proposed fix
-
AT:
- rename existing TaskForm bean to `camundaTaskForm` (without the dot). Make this the new "official" name of the bean (ie. use it in documentation examples etc.)
- for backwards compatibility provide subclass `@Named("camunda.taskForm")` using the same pattern as for the FoxTaskForm bean.
- Adjust documentation & quickstart
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-1587 Use JSF parameterMap instead of <viewParam> to avoid problems with JSF validation
-
- Closed
-