Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: softfail (athena.apache.org: transitioning domain of
 omgolafguhl@gmail.com does not designate 216.139.236.26 as permitted sender)
Date: Thu, 20 Mar 2014 10:24:52 -0700 (PDT)
From: Olaf <omgolafguhl@gmail.com>
To: users@camel.apache.org
Message-ID: <1395336292034-5749157.post@n5.nabble.com>
Subject: bean members with parallel processing
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello,

would the following route work correctly with multiple threads? In
beanRef("TestProcessor", "step2") the instance variable mapper is used, so I
suppose it is not thread safe, right? Should I set the mapper as a property
of the exchange?

        from(inputsource)
            .beanRef("TestProcessor", "step1")
            .beanRef("TestProcessor", "step2")
            .beanRef("TestProcessor", "step3")
            .log("${body}")


package testcamel;

import java.util.Map;
import org.apache.camel.Headers;

public class TestProcessor {

    private String generator;
    private JsonMapper mapper;

    public String step1(String filedata, @Headers Map headers) {
        //create mapper for each new message
        mapper = new JsonMapper();
        //do something here
        return "resultFromStep1";

    }

    public String step2(String contentFromStep1) {
        //do something here with mapper
        mapper.doSomething();
        return "resultFromStep2";
    }

    public String step3(String contentFromStep2) {
        //do something here with mapper
        mapper.doSomething();
        return "resultFromStep2";
    }

}


--
View this message in context: http://camel.465427.n5.nabble.com/bean-members-with-parallel-processing-tp5749157.html
Sent from the Camel - Users mailing list archive at Nabble.com.