Datacage: Add a pool of builders to make it multi threadable. XML DOM is not thread safe. Therefore the old implementation only allowed one thread to use the builder at a time. As the complexity of the configuration has increased over time this has become a bottleneck of the whole application because it took quiet some time to build a result. Furthermore the builder code path is visited very frequent. So many concurrent requests were piled up resulting in long waits for the users. To mitigate this problem a round robin pool of builders is used now. Each of the pooled builders has an independent copy of the XML template and can be run in parallel. The number of builders is determined by the system property 'flys.datacage.pool.size'. It defaults to 4.

package de.intevation.flys.artifacts.access;

import java.util.ArrayList;
import java.util.Arrays;
import java.util.List;

import de.intevation.artifacts.CallContext;
import de.intevation.flys.artifacts.FLYSArtifact;


public class MapAccess
extends RangeAccess
{

    public MapAccess(FLYSArtifact artifact, CallContext context) {
        super(artifact, context);
    }

    public List<String> getHWS() {
        String param = getString("uesk.hws");
        if (param != null) {
            String[] split = param.split(";");
            return new ArrayList<String>(Arrays.asList(split));
        }
        return new ArrayList<String>();
    }
}