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

[kurt.stam@jboss.com]

I really don't like leaving the configuration denormalized, but I have taken Tom's arguments to heart and I think I have found the 'happy medium'. In it I have simply nested the host/server/service. I think this flows much better and I think it is very close to what Tom was already working on but taking it one step up in the hierarchy (bringing hosts and servers back).


  | <hosts>
  | 	<host name="filebank" dnsName="localhost">
  | 		<servers>
  | 			<server name="fileBankServer" host="fileBank">
  | 			    <properties>
  | 				<property name="java.naming.provider.url" value="localhost:1099"/>
  | 				<property name="java.naming.factory.initial" value="org.jnp.interfaces.NamingContextFactory"/>
  | 				<property name="java.naming.factory.url.pkgs" value="org.jboss.naming:org.jnp.interfaces"/>
  | 			    </properties>
  | 			    <buses>
  | 			        <bus name="bank-jms-channel" server="fileBankServer" resourceType="QUEUE" userName="" password=""/>
  | 			        <bus name="bank-ftp-channel" server="inhouse-jboss-4.0.4" resourceType="FTP" userName="kurt" password="secret"/>
  | 			    </buses>
  | 			    <services>
  | 			        <service name="filebank-gateway" category="gateway" server="loanbroker-listener" description="This listener picks up files deposited by the fileBank"
  | 			        	class="org.jboss.soa.esb.FileBankGateway">
  | 			        	<listeners>
  | 			        	    	<listener description="A File-Based listener" bus="bank-ftp-bus"/>
  | 			        	    	<listener description="A JMS-Based listener" bus="bank-jms-bus"/>
  | 			        	</listeners>
  | 			        	<actions>
  | 			        	    <action name="TestDefaultRouteAction" process="route" class="org.jboss.soa.esb.actions.CbrProxyAction" service-category="MessageRouting"
  | 			    		    service-name="ContentBasedRoutingService" />
  | 			    	    	</actions>
  | 			        </service>
  | 			    </services>
  | 			</server>
  | 			<server name="inhouse-jboss-4.0.4">
  | 			    <properties>
  | 				<property name="java.naming.provider.url" value="localhost:1099"/>
  | 				<property name="java.naming.factory.initial" value="org.jnp.interfaces.NamingContextFactory"/>
  | 				<property name="java.naming.factory.url.pkgs" value="org.jboss.naming:org.jnp.interfaces"/>
  | 			    </properties>
  | 			    <services>
  | 			</server>
  | 			<server name="loanbroker-listener" host="loanbroker"/>
  |     		</servers>
  | 	</host>
  | 	<host name="jmsbank"  dnsName="localhost"/>
  | 	<host name="loanbroker" dnsName="localhost"/>
  | 	<host name="jms-provider" dnsName="localhost"/>
  |     </hosts>
  |     

So for instance the jndi information for the service or bus is simply found in the encapsulating server element.

Question, should a 'bus' be a type of service? I tend to think it is actually.

--Kurt

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3994215#3994215

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3994215