4 Replies Latest reply on Nov 7, 2005 2:25 PM by kva

    Process definition editor not showing up

    kva

      Hi,

      In an eclipse 3.1.1 installation with both MyEclipse 4.0.0 and jBPM GPD 3.0.4 in it, I cannot open the process definition with the process definition editor. The MyEclipse XML editor is used. Looking in the context menu "Open With", it seems the process definition editor does not even appear.

      Any idea how to make the two work together?

      Thanks for helping,
      Kristof

        • 1. Re: Process definition editor not showing up
          kukeltje

          search the forum. Question has been answered before. You need to link the gpd.xml and processdefinition.xml to the gpd. You can do that in the eclipse config

          • 2. Re: Process definition editor not showing up
            kva

            First, I did search the forum (gpd content type, gpd file association, gpd myeclipse,...) without resolve.

            Anyway, I looked at the 'Content Types' and both the processdefinition-xml and gpd-xml entries are present.

            I looked at the 'File Associations' and under *.xml the jBPM GPD is listed.

            I explicitly added gpd.xml and processdefinition.xml and set the GPD as default. After doing so, the icons changed from the X-type xml icon into the P-type GPD icon. But when looking at the properties of the file, its content is still identified as MyEclipse XML content type.

            Even when creating a new process project the files are identified as MyEclipse XML content.

            Any other suggestions?

            • 3. Re: Process definition editor not showing up
              kukeltje

              unfortunately not. That is what I did and it worked for me. Maybe try ME 4.02.

              • 4. Re: Process definition editor not showing up
                kva

                Ok, got it working now. Closing all the editors and then adding explicit mappings for both gpd.xml and processdefinition.xml to the GPD editor seems to solve it. The type of the xml files is still reported to be MyEclipse XML type content in the properties dialog but that is probably harmless.