[jboss-dev-forums] [Design of JBoss ESB] - Re: Configuration - normalization

Not to bring up the whole configuration concepts up again but what about generalizing the providers and listeners? The reason I say this is that as you start to experiment with different listeners (protocols and transports) the way to configure them should be easy to add. The listeners especially as this could start to become a large set of variations. For example, currently the configuration is: | <ftp-provider some-ftp-provider-prop="blah-ftp-prop" ..... > | <!-- | See how we specify a filter for this FTP bus at the listener level. Look | for listeners the use the "blah-ftp-bus" jus. | --> | <ftp-bus busid="blah-ftp-bus" some-ftp-bus-param="x"/> | </ftp-provider> And: | | <jms-listener name="Auditing-JMS-Gateway" | is-gateway="true" | busidref="y-queue" | maxThreads="1"/> Why not just generalize it to be: | <provider type="ftp" (optionally implementation="com.xyz.MyFTPProvider" )> | <attribute name="some-ftp-provider" value="22" /> | <bus id="blah-ftp-bus"> | <attribute name="some-ftp-provider" value="22" /> | <message-filter > | <attribute name="dir" value="Reconcilation" /> | </message-filter> | </bus> | </provider> And: | | <listener name="Auditing-FTP-Gateway" | is-gateway="true" | busidref="blah-ftp-bus" | maxThreads="1"/> Just some thoughts as this would make it consistent across configuring providers and listeners. It also makes the tooling support become easier as you can just have a template of attribtutes for a given provider and listener. It also cleans up some of the listener/bus code in dealing a little. Thoughts? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4024201#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...