2 Replies Latest reply on Feb 18, 2010 7:55 AM by matsonb

    JBoss ESB editor destroys NotifyEmail

      I've tried this with both the 3.1.CR1 version and the nightly from the trunk.  For the 4.5 version of the ESB (what we're running), the following is a setup for a dummy service containing an email notifier:

       

      <?xml version="1.0"?>
      <jbossesb parameterReloadSecs="5"
      xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.1.0.xsd"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.1.0.xsd http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schemas/xml/jbossesb-1.1.0.xsd">
      <services>
        <service category="TestCategory" description="Test" invmScope="GLOBAL" name="TestService">
         <actions>
          <action class="org.jboss.soa.esb.actions.Notifier" name="TestNotifier">
           <property name="destinations">
            <NotificationList type="OK">
             <target class="NotifyEmail" sendTo="person@somewhere.com"/>
            </NotificationList>
           </property>
          </action>
         </actions>
        </service>
      </services>
      </jbossesb>

       

      As far as I can tell from both the documentation and the code in the org.jboss.soa.esb.notification.NotifyEmail class, the code HAS to have the from/sendTo, etc in the attributes of the <target> tag.  If you pull the above into the current development ESB editor, and make a change on the "tree" tab, then save, the sendTo (and any other attribute) gets removed from the XML.

       

      This behavior by JBoss tools is causing loss of vital pieces of the ESB configuration since there does not appear to be a way of configuring the NotifyEmail class in the 4.5 version of the ESB except by these attributes.  Is there another way the NotifyEmail class is supposed to be configured, or is this a problem in tools?