topic Parsing custom extensionElements in 5.12 in Alfresco Archive

Parsing custom extensionElements in 5.12

das — Thu, 07 Mar 2013 20:47:07 GMT

Hi,I'm using custom <extensionElements> to create taskListeners for specific tasks.In 5.11 I'm using a BpmnParseListener and reading the tags via "taskElement.element("extensionElements").elementsNS(..)".I tried the new BpmnParseHandler, but the XML information is not available.As far as I cou

Re: Parsing custom extensionElements in 5.12

pkromolowski — Thu, 14 Mar 2013 13:41:37 GMT

I have the same problem. Is there a way to access the XML structure directly from BpmnParseHandlers?

Thanks.

Re: Parsing custom extensionElements in 5.12

jbarrez — Fri, 15 Mar 2013 09:33:58 GMT

It seems we have not completely made the new approach backwards compatible with the old one. The new BPMN model classes don't expose it currently. I'll make sure we add it.

Unfortunately, this means 5.12 is not usable for you if you depend on that feature. You could always try to fetch the xml yourself and parse it, but that is really cumbersome of course…

Re: Parsing custom extensionElements in 5.12

pkromolowski — Fri, 15 Mar 2013 10:18:56 GMT

Thank you! Does it mean that we may expect this feature in 5.13 or in some "intermediate" builds?

Re: Parsing custom extensionElements in 5.12

das — Sat, 16 Mar 2013 08:45:27 GMT

Thank you for the answer.

I'll keep using 5.11 until this is added.

Re: Parsing custom extensionElements in 5.12

jbarrez — Mon, 18 Mar 2013 15:46:35 GMT

Thank you! Does it mean that we may expect this feature in 5.13 or in some "intermediate" builds?

Yes, it is important enough to fix it for 5.13. We might indeed push out a stable snapshot version in a few weeks.

Re: Parsing custom extensionElements in 5.12

conradi — Tue, 30 Apr 2013 11:28:32 GMT

I just wanted to add that we have the same issue.

For an intermediate solution, it would even suffice to patch our local activiti with the appropriate git commit.

Re: Parsing custom extensionElements in 5.12

conradi — Tue, 30 Apr 2013 11:39:21 GMT

There is the same problem when trying to get custom attributes of a Task.

Re: Parsing custom extensionElements in 5.12

trademak — Wed, 01 May 2013 09:43:47 GMT

Yes, this is on our roadmap for 5.13. We'll try to add the necessary functionality ASAP.

Best regards,

Re: Parsing custom extensionElements in 5.12

sebastian_s — Thu, 16 May 2013 07:38:12 GMT

I could not find the JIRA issue for this problem. Please point me to the JIRA issue.

Thanks.

Re: Parsing custom extensionElements in 5.12

sebastian_s — Mon, 03 Jun 2013 11:38:44 GMT

Hello Tijs,

please point me to the JIRA issue.

Thanks a lot.

Sebastian

Re: Parsing custom extensionElements in 5.12

trademak — Tue, 04 Jun 2013 07:00:31 GMT

We have a JIRA related to the Designer, but to solve that we also need to fix it in the parser:

http://jira.codehaus.org/browse/ACT-1683

The work in the parser has been done already, we only need to upgrade the designer with the new JARs.
Would be good if you could give it a try on the current Github master version. There is a method getExtensionElements() that can be used to get the extension elements of a BPMN element.

Best regards,

Re: Parsing custom extensionElements in 5.12

pkromolowski — Thu, 20 Jun 2013 08:01:34 GMT

Hi,

I am now downloading Activiti 5.13, but I must ask you this question - did you manage to fix the issue above in the new version ? I couldn't find it in the Changelog and will only be able to check this out in the evening.

Thanks,
Przemek

Re: Parsing custom extensionElements in 5.12

pkromolowski — Thu, 20 Jun 2013 08:29:25 GMT

Ok, I couldn't wait and did a quick look into the new version. I can see that there is a org.activiti.bpmn.model.BaseElement.getExtensionElements() method, I suppose that this is what I sould use the read the extension elements. Am I right?

Thanks,

Re: Parsing custom extensionElements in 5.12

sebastian_s — Tue, 25 Jun 2013 19:07:55 GMT

Hello Tijs,

Sorrry, but I didn't take notice of your answer until now. Now that 5.13 has been released it's a bit late but I am sure I'll have a look at it since we also depend on extension elements. So thanks for the fix.

Przemek, thank you for keeping the rest on us on the forums updated on this.

Best regards!

Re: Parsing custom extensionElements in 5.12

jbarrez — Thu, 27 Jun 2013 09:30:04 GMT

Yes - it was added to 5.13.

Re: Parsing custom extensionElements in 5.12

rhafner — Tue, 09 Jul 2013 14:17:27 GMT

There appears be a limitation in the current implementation of org.activiti.bpmn.model.BaseElement.getExtensionElements(). Since it returns a Map<String,ExtensionElement> with the elementName as the key there isn't a way to parse multiple XML elements of the same type. Was this intended? If so, is there a recommended approach to model custom key/value extension elements to avoid this limitation? Thanks!

For example:
<code>
    <userTask id="usertask1" name="Task A">
     <extensionElements>
      <myext:attributes>
    <myext:attribute name="Attr1" value="1" />
    <myext:attribute name="Attr2" value="2" />
   </myext:attributes>
       </extensionElements>
    </userTask>
</code>

Re: Parsing custom extensionElements in 5.12

jbarrez — Thu, 11 Jul 2013 14:25:59 GMT

Seems indeed to be a limitation which shouldn't be there. After all the ExtensionElement class does have support for child elements.

I pinged Tijs (who wrote this code) to clarify/fix.

Re: Parsing custom extensionElements in 5.12

rhafner — Wed, 11 Sep 2013 18:53:07 GMT

Has a jira issue been opened for this limitation? If not, should I open one?

Re: Parsing custom extensionElements in 5.12

trademak — Thu, 12 Sep 2013 06:32:37 GMT

In this commit the issue was fixed, so it will be part of the next 5.14 release:

https://github.com/Activiti/Activiti/commit/6c0563799439dfa5ab662e51d9725649860a6d67

Best regards,