cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <>
Subject Re: Spring Configurator - filter/include strategy
Date Tue, 15 Jul 2008 14:51:27 GMT
Carsten Ziegeler wrote:
> Now I was very brief as I'm not 100% sure how the final solution in 
> jetspeed looks like.
> Ok, our spring configurator includes all files located at a specific 
> location and adds all bean definitions found there.
> The jetspeed guys enhanced the spring bean configuration format to have
> conditionals inside a bean xml definition, so something like (don't 
> quote me on the syntax):
> <j:if test="database.derby">
>   <bean name="database" ...the derby bean
> <j:if>
> <j:else>
>   <bean name="database" ...the hsqldb bean
> </j:else>
Wow. It looks like Maven 1 jelly code. Next you will see for loops and 
ant tasks!

I'm not crazy about XML as a programming language. The information 
needed to make decisions should be in the XML, not the logic.


View raw message