Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-6260

jndiName for notifier disappears if editing the xml directly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 3.1.1
    • 3.1.0.GA
    • esb
    • None
    • Hide

      To recreate
      1) Open an existing esb.xml file
      2) Select the source tab of the editor and edit the file. Press save
      3) Select the tree tab of the editor and open the notify action and expand each type
      The jndiName will be missing.
      If you then change anything else using the tree view, the jndiName elements are lost

      Show
      To recreate 1) Open an existing esb.xml file 2) Select the source tab of the editor and edit the file. Press save 3) Select the tree tab of the editor and open the notify action and expand each type The jndiName will be missing. If you then change anything else using the tree view, the jndiName elements are lost

      If I have an esb.xml file with a notifier as seen below, if I edit the xml file using the source tab and save, if I then return to the file and edit using the tree tab(forms), the <queue> element for the target elements get lost.

      <actions mep="RequestResponse">
      <action class="org.jboss.soa.esb.actions.Notifier" name="SendResponseNotifier">
      <property name="okMethod" value="notifyOK"/>
      <property name="exceptionMethod" value="notifyError"/>
      <property name="destinations">
      <NotificationList type="err">
      <target class="NotifyQueues">
      <queue jndiName="queue/MincomJMS_reply"/>
      </target>
      </NotificationList>
      <NotificationList type="ok">
      <target class="NotifyQueues">
      <queue jndiName="queue/MincomJMS_reply"/>
      </target>
      </NotificationList>
      </property>
      </action>

              scabanovich Viacheslav Kabanovich (Inactive)
              bblasko Brian Blasko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: