Bug 1072314 - Forms are not automatically generated for provided process from designer
Summary: Forms are not automatically generated for provided process from designer
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: CR1
: 6.0.1
Assignee: Pere Fernàndez
QA Contact: Jan Hrcek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-04 11:18 UTC by Pedro Zapata
Modified: 2014-08-06 20:02 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:02:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pedro Zapata 2014-03-04 11:18:36 UTC
#1 Clone repo https://github.com/pzapataf/kie-examples.git
#2 Open project 'CustomerFollowUp'
#3 Open process
#4 Try to generate all process froms. 

Nothing happens. 

It's likely there's some missing configuration in the process or task mappings, but there's no

The only log is 
12:05:46,520 ERROR [org.jbpm.designer.web.server.TaskFormsServlet] (http-localhost/127.0.0.1:8080-3) null

Comment 2 Pedro Zapata 2014-03-04 11:35:23 UTC
The error is caused in the following line in 


Path myPath = vfsServices.get( uuid );


Where uuid='default://master@rh-summit/Customer Satisfaction/src/main/resources/Customer Followup.bpmn2'

That causes the following exception:

java.net.URISyntaxException: Illegal character in path at index 35: default://master@rh-summit/Customer Satisfaction/src/main/resources/Customer Followup.bpmn2


It looks like it's a problem with the spaces in the resource name.

Also the exception reporting must be improved, just printing e.getMessage() filters out the error message and must be avoided at all cost.

   
   } catch (Exception e) {
            _logger.error(e.getMessage());
            ...
   }

Comment 3 Pedro Zapata 2014-03-04 12:12:47 UTC
Once fixed the space problem, it looks like another problem related to this arises. No .form files are automatically generated now, while .ftl are still genereated.

This can be verified with any process, for example 'Hiring process', by deleting existing forms and try to 'Generate all forms'.

Comment 4 Pere Fernàndez 2014-03-05 17:21:13 UTC
There was a problem when adding a field from non existing holder.

Commit (master): https://github.com/droolsjbpm/jbpm-form-modeler/commit/6a8c4863d9b4978c304d3f6704099ec84162db7e

Commit (6.0.x): https://github.com/droolsjbpm/jbpm-form-modeler/commit/6d4cb8381230c2832eb3fa87c658f5b6eb376db0

Comment 5 Marek Baluch 2014-03-06 12:50:09 UTC
Based on latest testing it's not possible to generate the forms one by one either.   Given there's no workaround setting severity to 'urgent'.

Comment 6 Jan Hrcek 2014-03-06 12:55:39 UTC
Just for completness: The problem is there not only when you click 'generate all forms' in designer, but also when you select a human task and click 'Generate Task form'. When that is clicked, only the process form is generated and the following stacktrace is shown in server log (pasting just the relevant part). Please make sure that both buttons for generating forms in designer work.

13:52:51,923 ERROR [org.jbpm.designer.taskforms.TaskFormTemplateManager] (http-localhost/127.0.0.1:8080-3) null
13:52:51,923 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) java.lang.NullPointerException
13:52:51,924 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.formModeler.core.config.FormManagerImpl.addDataFieldHolder(FormManagerImpl.java:562)
13:52:51,924 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.formModeler.core.config.FormManagerImpl.addDataHolderFields(FormManagerImpl.java:553)
13:52:51,924 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.formModeler.core.config.FormManagerImpl.addAllDataHolderFieldsToForm(FormManagerImpl.java:541)
13:52:51,924 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.formModeler.core.config.FormManagerImpl$Proxy$_$$_WeldClientProxy.addAllDataHolderFieldsToForm(FormManagerImpl$Proxy$_$$_WeldClientProxy.java)
13:52:51,925 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.formModeler.designer.integration.impl.BPMNFormBuilderServiceImpl.addHoldersToForm(BPMNFormBuilderServiceImpl.java:92)
13:52:51,925 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.formModeler.designer.integration.impl.BPMNFormBuilderServiceImpl.buildFormXML(BPMNFormBuilderServiceImpl.java:83)
13:52:51,925 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.formModeler.designer.integration.impl.BPMNFormBuilderServiceImpl$Proxy$_$$_WeldClientProxy.buildFormXML(BPMNFormBuilderServiceImpl$Proxy$_$$_WeldClientProxy.java)
13:52:51,925 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.designer.taskforms.TaskFormTemplateManager.generateUserTaskTemplate(TaskFormTemplateManager.java:424)
13:52:51,925 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.designer.taskforms.TaskFormTemplateManager.generateTemplates(TaskFormTemplateManager.java:382)
13:52:51,925 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.designer.taskforms.TaskFormTemplateManager.processTemplates(TaskFormTemplateManager.java:100)
13:52:51,925 ERROR [stderr] (http-localhost/127.0.0.1:8080-3) 	at org.jbpm.designer.web.server.TaskFormsServlet.doPost(TaskFormsServlet.java:100)

Comment 7 Kris Verlaenen 2014-03-06 23:25:21 UTC
Pere, could you check the new comments?

Comment 8 Pere Fernàndez 2014-03-07 12:15:20 UTC
The error that causes the traces is already fixed on my previous commits.

I also fixed the bug on the designer that creates the process form when the user presses "Generate Task Form".

Commit (master): https://github.com/droolsjbpm/jbpm-designer/commit/57cbf7eb61f63dde7a6e98caf2ffc7fd16367a00

Commit (6.0.x): https://github.com/droolsjbpm/jbpm-designer/commit/91f4405743f21d1bee6dc2f6e6b98d8118021ecc

Comment 9 Michael 2014-03-17 11:56:15 UTC
Ticket cherry-picked into 6.0.1.CR1. 
Commit: 3dbd49eadd17f9a48d2033af81584f510b7dd48e

Comment 10 Jan Hrcek 2014-03-24 07:24:00 UTC
Ok, verified with BPMS 6.0.1 CR1


Note You need to log in before you can comment on or make changes to this bug.