Uploaded image for project: 'Red Hat CodeReady Studio (devstudio)'
  1. Red Hat CodeReady Studio (devstudio)
  2. JBDS-1258

ESB Editor generates wrong value for command attribute and wrong property name for process definition name.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Duplicate
    • Minor
    • 4.0.0.M1
    • 3.0.0.GA
    • integration-platform
    • None
    • Hide

      1. Start a ESB Project
      2. Add a Service
      3. Add a BPM Processor action
      4. Select "StartProcessCommand" as command
      5. specify process name

      Show
      1. Start a ESB Project 2. Add a Service 3. Add a BPM Processor action 4. Select "StartProcessCommand" as command 5. specify process name
    • Workaround Exists
    • Hide

      Change manually

      Show
      Change manually
    • Low

    Description

      When using ESB Editor to add a BPM Processor the drop-down for command contains the option "StartProcessCommand" which should be "StartProcessInstanceCommand". The following is the xml generated by the BPM Processor:

      <action class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor" name="start-bpm-process">
      <property name="command" value="StartProcessCommand"/>
      <property name="processdefinition" value="testproc"/>
      </action>

      To get this to work with JBoss SOA-P 5 it should read:
      <action class="org.jboss.soa.esb.services.jbpm.actions.BpmProcessor" name="start-bpm-process">
      <property name="command" value="StartProcessInstanceCommand"/> <!-- Property value changed -->
      <property name="process-definition-name" value="testproc"/> <!-- Property name changed -->
      </action>

      Attachments

        Issue Links

          duplicates

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-6059 jboss-esb.xml editor and process definition

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-6201 BpmProcessor action: wrong list of commands

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              scabanovich Viacheslav Kabanovich (Inactive)
              rhn-sa-tqvarnst Thomas Qvarnström
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: