conditional processing

**mperham** · Aug 30th, 2004, 09:01 PM

Overriding is allowed. That's the whole point - your test context just overrides the few beans which need to change for your unit tests. 90% of your context stays the same and you don't have to maintain two separate copies of the same context.

Originally Posted by memelet

No, because I am including the entire production-context.xml into the appcontext along with the integration-context.xml and doing what you showed would be defining two beans of the same id. (Or is allowed to override an existing bean id?)

**bryanhunt** · Aug 31st, 2004, 03:48 AM

Hello all,
I am sure there is a neater or better way to implement this but it is
working for me. There is no testcase but I have tested this using the
"main" method.

This code is free for anyone to use and I would be delighted if it was
included in spring.

/*
* Created on 30 août 2004
*/
package ie.jestate.temp.spring;

import java.util.HashMap;
import java.util.HashSet;
import java.util.Iterator;
import java.util.Map;
import java.util.Set;

import org.springframework.beans.BeansException;
import org.springframework.context.support.AbstractXmlApp licationContext;

/**
* @author Administrateur
*
*/
public class ConditionalClassPathXMLApplicationContext
extends AbstractXmlApplicationContext {

public static void main(String[] args) {

Map mappings = new HashMap();
mappings.put("jestate.testing=true","classpath:tes t/ie/jestate/applicationContext-hibernate.xml");
mappings.put("jestate.db=true","classpath:test/ie/jestate/applicationContext-hibernate.xml");
mappings.put("jestate.anothervar=true","classpath: test/ie/jestate/anothervar.xml");
Map variables = new HashMap();
variables.put("jestate.testing","true");
variables.put("jestate.db","false");
variables.put("jestate.anothervar","false");

ConditionalClassPathXMLApplicationContext test = new ConditionalClassPathXMLApplicationContext(mappings ,variables);
}

private String[] configLocations ;

public ConditionalClassPathXMLApplicationContext(Map mappings, Map variables)
throws BeansException {

Set mappingKeys = mappings.keySet();
Set variableKeys = variables.keySet();
Set configLocationSet = new HashSet();
Iterator variableKeysIterator = variableKeys.iterator();

while (variableKeysIterator.hasNext()) {

String variableKey = (String ) variableKeysIterator.next();
String mapping = (String) variables.get(variableKey);
String mappingKey = variableKey + "=" + mapping;
logger.debug("mappingKey='" + mappingKey + "'");
logger.debug("mappings.get(mappingKey)='" + mappings.get(mappingKey) + "'");
if(mappings.get(mappingKey) != null) {
configLocationSet.add(mappings.get(mappingKey));
}
}

configLocations = new String[configLocationSet.size()];

Iterator iterator = configLocationSet.iterator();

configLocations = (String[]) configLocationSet.toArray(configLocations);

for (int ii = 0; ii < configLocations.length; ii++) {
logger.debug(configLocations[ii]);
}
refresh();
}

/* (non-Javadoc)
* @see org.springframework.context.support.AbstractXmlApp licationContext#getConfigLocations()
*/
protected String[] getConfigLocations() {
return configLocations;
}
}

**memelet** · Aug 31st, 2004, 07:30 AM

Originally Posted by mperham

Overriding is allowed. That's the whole point - your test context just overrides the few beans which need to change for your unit tests. 90% of your context stays the same and you don't have to maintain two separate copies of the same context.

Cool! Thanks.

**bryanhunt** · Aug 31st, 2004, 08:40 AM

Originally Posted by mperham

But spring already supports this in a much cleaner method (IMO) without conditionals by just specifying the context files you want to use:

Code:

        ClassPathXmlApplicationContext ctx = new ClassPathXmlApplicationContext&#40;
                new String&#91;&#93; &#123;"applicationContext-domain.xml", 
                                    "applicationContext-domain-test.xml" &#125;&#41;;

Where domain is my live configuration and test overrides certain values in it to use a Hypersonic VM db instead. The override capability is why you don't need conditionals.