That won't be a problem; the option is scoped to the calling thread. It's stored in a ThreadLocal and is cleared when the next call to the cache after it's set returns. Admittedly, it's a clunky API. In JBC 1.x the Option was passed as a method param in an overloaded method, which was more intuitive but added tons of overloaded methods. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225473#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...