[JBoss JIRA] Created: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
12:31 p.m.
jPDL schema does not contain an attribute "description" for the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:35 p.m.
New subject: [JBoss JIRA] Commented: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Sebastian Schneider commented on JBPM-2554:
-------------------------------------------
This is sufficient to make process definitions valid again when using descriptions for
tasks.
<attribute name="description" type="string"
default="">
<annotation><documentation>the description of the
task</documentation></annotation>
</attribute>
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:02 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Ronald van Kuijk reassigned JBPM-2554:
--------------------------------------
Assignee: Ronald van Kuijk
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Assignee: Ronald van Kuijk
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:19 a.m.
New subject: [JBoss JIRA] Assigned: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Tom Baeyens reassigned JBPM-2554:
---------------------------------
Assignee: Tom Baeyens (was: Ronald van Kuijk)
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Assignee: Tom Baeyens
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:46 a.m.
New subject: [JBoss JIRA] Resolved: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Tom Baeyens resolved JBPM-2554.
-------------------------------
Resolution: Done
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Assignee: Tom Baeyens
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 a.m.
New subject: [JBoss JIRA] Reopened: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Sebastian Schneider reopened JBPM-2554:
---------------------------------------
I reopen this issue. The description of the bug is incorrect / incomplete since the
parsing of the description for task elements was also not taken care of in jBPM 4.1.
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Assignee: Tom Baeyens
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:19 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2554:
--------------------------------------
Description:
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
The attribute is not only missing in the schema but it was also forgotten when the parsing
of a process definition is done. So the member "description" of a task-object is
always null.
was:The jPDL schema defintion does not contain an attribute named description for the
element task. It was just left out. You find a changed schema file attached. Should
description be an attribute anyway but rather an element in task? Might be more
comfortable with bigger descriptions when hand-editing process definitions. I have no clue
how exactly the parsing of the file is done in the engine so I do not know if this would
be a major change. For now it would be great to account for the attribute
"description" and get this change into the 4.2 release.
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Assignee: Tom Baeyens
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
The attribute is not only missing in the schema but it was also forgotten when the
parsing of a process definition is done. So the member "description" of a
task-object is always null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:21 a.m.
New subject: [JBoss JIRA] Updated: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Sebastian Schneider updated JBPM-2554:
--------------------------------------
Workaround Description:
Of course you can just use the description-attribute since deployment and parsing still
works then but it is very uncomfortable in the GPD or if you want to validate process
definitions against the schema.
Attention: Parsing of process definitions works but the description is not read.
was:Of course you can just use the description-attribute since deployment and parsing
still works then but it is very uncomfortable in the GPD or if you want to validate
process definitions against the schema.
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Assignee: Tom Baeyens
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
The attribute is not only missing in the schema but it was also forgotten when the
parsing of a process definition is done. So the member "description" of a
task-object is always null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:40 a.m.
New subject: [JBoss JIRA] Closed: (JBPM-2554) jPDL schema does not contain an attribute "description" for the element task
[
https://jira.jboss.org/jira/browse/JBPM-2554?page=com.atlassian.jira.plug...
]
Tom Baeyens closed JBPM-2554.
-----------------------------
Resolution: Done
i added description as sub element of activities, process, swimlane and a couple of other
elements
jPDL schema does not contain an attribute "description" for
the element task
----------------------------------------------------------------------------
Key: JBPM-2554
URL: https://jira.jboss.org/jira/browse/JBPM-2554
Project: jBPM
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Runtime Engine
Affects Versions: jBPM 4.1
Environment: not relevant
Reporter: Sebastian Schneider
Assignee: Tom Baeyens
Fix For: jBPM 4.2
The jPDL schema defintion does not contain an attribute named description for the element
task. It was just left out. You find a changed schema file attached. Should description be
an attribute anyway but rather an element in task? Might be more comfortable with bigger
descriptions when hand-editing process definitions. I have no clue how exactly the parsing
of the file is done in the engine so I do not know if this would be a major change. For
now it would be great to account for the attribute "description" and get this
change into the 4.2 release.
The attribute is not only missing in the schema but it was also forgotten when the
parsing of a process definition is done. So the member "description" of a
task-object is always null.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5539
days inactive
5572
days old
8 comments
3 participants
participants (3)
-
Ronald van Kuijk (JIRA) -
Sebastian Schneider (JIRA)
-
Tom Baeyens (JIRA)