HOWTO: enable content assist in GPD XML editor

[avbentem]

I'm not sure if there's a better way, but to enable content assist for the process definitions in the Graphical Process Designer:

- Eclipse, Preferences
- Web and XML
- XML catalog
- User specified entries, click Add
- URI: http://docs.jboss.org/jbpm/xsd/jpdl-3.2.xsd
- Key Type: Namespace Name
- Key:urn:jbpm.org:jpdl-3.2

This enables content assist for:

<?xml version="1.0" encoding="UTF-8"?>
<process-definition name="my-process" xmlns="urn:jbpm.org:jpdl-3.2">
:
</process-definition>

Of course, without making any chances to Eclipse preferences, or when using other tools, one could also explicitly specify the location:

<?xml version="1.0" encoding="UTF-8"?>
<process-definition name="my-process" xmlns="urn:jbpm.org:jpdl-3.2"
 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation=
 "urn:jbpm.org:jpdl-3.2 http://docs.jboss.org/jbpm/xsd/jpdl-3.2.xsd">
:
</process-definition>

Note that in both cases using xmlns="urn:jbpm.org:jpdl-3.2" will enable runtime XML validation, under some conditions, as described in 16.4.1. Validation in the documentation.

Arjan.

[avbentem]

"avbentem" wrote:
URI: http://docs.jboss.org/jbpm/xsd/jpdl-3.2.xsd

Note that, for version 3.1, the shorthand http://jbpm.org/jpdl-3.1.xsd was used in the documentation, which redirects to http://docs.jboss.org/jbpm/xsd/jpdl-3.1.xsd -- but for 3.2 no such shorthand (yet) exists: http://jbpm.org/jpdl-3.2.xsd.

"avbentem" wrote:
This enables content assist

...but now tells me that the binding attribute is not in the 3.2 schema. That will teach me not trying to be lazy ;-)

<process-state name="My sub-process">
 <sub-process name="my-sub-process" binding="late" />
 <transition name="end" to="End"></transition>
</process-state>

Reported; JBPM-910.

[kukeltje]

I admire your contributions... Bugfixes, howtos etc...This one, I'll make a wiki page of this myself !!! (yes, I'll do it)

[koen.aers]

Arjan,

Thanks for pointing this out. This is indeed a correct way of enabling the content assist. The problem is in fact a bug in the GPD that will be fixed.

Regards,
Koen