flowable / flowable/flowable-engine
Flowable Modeler - Group names with spaces (e.g., Team Leader, Team Member)
- Lingua principale
- Java
- Stelle
- 9.5k
- Fork
- 2.9k
- Merge medio
- 7h 8m
- PR unite (30g)
- 2
Descrizione
In my [application](https://github.com/Robinyo/serendipity) I have created two groups (i.e., 'Team Leader', 'Team Member'), [flowable.ldif](https://github.com/Robinyo/serendipity-api/blob/master/projects/spring-boot/server/services/openldap/ldif/flowable.ldif):
```
...
# Groups
dn: cn=Team Leader, ou=groups, dc=flowable,dc=org
changetype: add
objectclass: top
objectclass: groupOfUniqueNames
cn: Team Leader
ou: Team Leader
uniqueMember: uid=rob.ferguson,ou=users,dc=flowable,dc=org
dn: cn=Team Member, ou=groups, dc=flowable,dc=org
changetype: add
objectclass: top
objectclass: groupOfUniqueNames
cn: Team Member
ou: Team Member
uniqueMember: uid=rob.ferguson,ou=users,dc=flowable,dc=org
uniqueMember: uid=sean.doyle,ou=users,dc=flowable,dc=org
uniqueMember: uid=robert.russo,ou=users,dc=flowable,dc=org
```
And, the [groups](https://github.com/Robinyo/serendipity-api/blob/master/projects/spring-boot/docs/administrator/flowable.md) are available for assignment as candidate groups in Flowable Modeler:

However, the generated BPMN file has a space in the attribute name (group-info-name-Team Leader):
```
...
```
Which cannot be parsed by the BPMN deployer:
```
...
2020-08-29 08:13:04.034 INFO 31421 --- [ main] o.s.s.c.ThreadPoolTaskScheduler : Initializing ExecutorService
2020-08-29 08:13:04.043 INFO 31421 --- [ main] o.f.a.engine.impl.deployer.AppDeployer : Processing app resource case-management.app
2020-08-29 08:13:04.132 INFO 31421 --- [ main] o.f.e.c.impl.deployer.BpmnDeployer : BpmnDeployer: processing resource case-planning.bpmn
2020-08-29 08:13:04.135 INFO 31421 --- [ main] o.f.e.c.impl.deployer.BpmnDeployer : BpmnDeployer: processing resource case-monitoring.bpmn
2020-08-29 08:13:04.135 INFO 31421 --- [ main] o.f.e.c.impl.deployer.BpmnDeployer : BpmnDeployer: processing resource case-Identification-and-assessment.bpmn
2020-08-29 08:13:04.135 INFO 31421 --- [ main] o.f.e.c.impl.deployer.BpmnDeployer : BpmnDeployer: processing resource case-evaluation-and-outcomes.bpmn
ERROR: 'ParseError at [row,col]:[8,46]
Message: Attribute name "Leader" associated with an element type "modeler:group-info-name-Team" must be followed by the ' = ' character.'
2020-08-29 08:13:04.395 ERROR 31421 --- [ main] o.f.e.i.b.d.ParsedDeploymentBuilder : Could not parse resource case-evaluation-and-outcomes.bpmn
org.flowable.bpmn.exceptions.XMLException: javax.xml.transform.TransformerException: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[8,46]
Message: Attribute name "Leader" associated with an element type "modeler:group-info-name-Team" must be followed by the ' = ' character.
```
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Direzione di ricerca
Inizia con la risorsa generata case-evaluation-and-outcomes.bpmn e con l'elemento malformato modeler:group-info-name-Team Leader mostrato nel report, quindi riproduci il deployment usando la configurazione del gruppo Team Leader fornita. Traccia i metadati candidate-group generati da Modeler e verifica che i nomi dei gruppi contenenti spazi producano XML BPMN valido che il deployer possa analizzare.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- backend
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 35/100