view flys-client/src/main/java/de/intevation/flys/client/server/RemoveArtifactServiceImpl.java @ 5779:ebec12def170

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.
author Sascha L. Teichmann <teichmann@intevation.de>
date Sun, 21 Apr 2013 12:48:09 +0200
parents bc06a671ef60
children
line wrap: on
line source
package de.intevation.flys.client.server;

import org.apache.log4j.Logger;

import de.intevation.flys.client.shared.exceptions.ServerException;
import de.intevation.flys.client.shared.model.Collection;
import de.intevation.flys.client.client.services.RemoveArtifactService;


/**
 * Implementation of RemoveArtifactService .
 */
public class RemoveArtifactServiceImpl
extends      DescribeCollectionServiceImpl
implements   RemoveArtifactService
{
    private static final Logger logger =
        Logger.getLogger(RemoveArtifactServiceImpl.class);


    public Collection remove(
        Collection collection,
        String     artifactId,
        String     locale)
    throws ServerException
    {
        logger.info("RemoveArtifactServiceImpl.remove");

        String url = getServletContext().getInitParameter("server-url");

        return CollectionHelper.removeArtifact(collection, artifactId, url, locale);
    }
}
// vim:set ts=4 sw=4 si et sta sts=4 fenc=utf8 :

http://dive4elements.wald.intevation.org