1 2 Previous Next 20 Replies Latest reply on Sep 18, 2009 4:42 AM by Koen Aers Go to original post
      • 15. Re: Creating domain specific nodes into a jbpm-editor
        Ronald van Kuijk Master

        Oh, and in addition for the really new nodes, I think the jbpm config jbpm.jpdl.activities.xml file should be extended with an e.g. include file right?

        So there are really two ways then, where the 'custom' node one almost needs all that for the really new nodes (correct me if I'm wrong) and maybe even a little more on the GPD side.

        • 16. Re: Creating domain specific nodes into a jbpm-editor
          Koen Aers Master

          Ok, I see indeed the need to have the class on the classpath in the case of a custom node if the target users are developers and want to write unit tests and deploy the processes. In this case I would think that a preference page that lets you add the jars containing the additional classes would be a great first step. On the other hand, if the target users are only analists, you probably don't want this preference page and would rather drop the plugin.xml files in your eclipse.

          The problem of the bloated palette should in my opinion as well be solved by yet another preference page that lets you enable/disable the nodes for that particular workspace.

          Makes sense?

          Cheers,
          Koen

          • 17. Re: Creating domain specific nodes into a jbpm-editor
            Jan Bartel Newbie

            Hey everybody,

            at first sorry for my absence in the last week which was the result of unexpected project pressure in the last 4 days, but since this is managed, I hope to spend my next 3 days into the extension of the GPD ....

            As the things are now, I managed to check out the 4 projects in the jboss-svn at the last weekend and get a better view about eclipse-plugin-developement. With this new knowledge in mind I would agree to Koen that having a plugin-based way to extend the gpd with customized nodes would be great, and would also agree with Ronald
            that having a way to extend it without plugins would also be great.

            So why shouldn't we implement both way's ?
            Since we have to refactor the classes which are responsible for registering the nodes and showing them into the editor-palette it should be easy to do both, requesting spezified extension points, which will satisfy the situation where you don't want some additional classes in your "design-project", and interspecting project classes for annotated customized node classes for situations where you want unit testing and a more "eclipse independent" developement.

            I will have a closer look at the both classes koen specified in the next hours and at tommorrow morning so that I hope that I can join in the discussion in a better way at saturday.

            Which takes me to the next point should I create a wiki-page for our "delineation" or will we discuss that at the GPD 292 ?

            Again sorry for being silent for the last week,

            Cheers,
            Jan







            • 18. Re: Creating domain specific nodes into a jbpm-editor
              Koen Aers Master

               

              "jan" wrote:
              Which takes me to the next point should I create a wiki-page for our "delineation" or will we discuss that at the GPD 292 ?


              I would prefer for the discussion to continue in GPD 292.

              "jan" wrote:
              Again sorry for being silent for the last week


              Hey, we're already glad that you want to collaborate!

              Cheers,
              Koen









              • 19. Re: Creating domain specific nodes into a jbpm-editor
                Ronald van Kuijk Master

                 

                So why shouldn't we implement both way's ?


                Sorry for not making that clear, but that was my intention from the beginning. But I think 'my way' should be done first (although gpd wise you need the other way also) but you do not need to document the way to extend the jpdl core in that case.

                The "delineation" can be put on a wiki page, but discussing in these kinds of 'broad' jira issues is not good I think. Discussing can either be done in separate topics on the dev forum or on #jbpm on irc.codehouse.org (easy for quick questions).

                • 20. Re: Creating domain specific nodes into a jbpm-editor
                  Koen Aers Master

                  The technical discussion should continue on GPD 292. Subtasks of this task may be created to indicate a division of the work. The subtasks can be based on what we already discussed here.
                  - defining additional extension points
                  - refactoring the two classes
                  - creating a preference page to add 'jPDL4 plugins'
                  I agree that the 'Ronald way' is more important and handy. So the first task that is needed is probably the creation of a jPDL4 plugin preference page. The second one is the refactoring of the PaletteFactory to account for these plugins.

                  Regards,
                  Koen

                  1 2 Previous Next