> So if you really need new steps classes (and others)
> per thread - then what I'm not sure about is how we
> get the candidate steps in the configuration to be
> thread-specific...I'd have to think about that
> design a bit more...
My ideal is that the startup phase of JBehave deals with class-defs (kinda like DI containers do). Later when instances are needed for step execution, they are acquired from one of: Pico, Spring, Guice, Weld ... or a default non-DI JBehave container where everything was pre-instantiated.