Could you please raise a JIRA issue for this?
On 28/03/2014 11:59, Hans Schwäbli wrote:
I could cache the embedder myself by using lazy initialization in my
class which extends JUnitStories.
But that has a side effect: the meta filtering does not work then for
some unknown reason.
On Wed, Mar 26, 2014 at 8:54 AM, Hans Schwäbli
<bugs.need.love....@gmail.com <mailto:bugs.need.love....@gmail.com>>
wrote:
Hello Mauro,
I stumbled upon a beheavior of this method:
org.jbehave.core.ConfigurableEmbedder.configuredEmbedder()
It always calls these methods when being called:
embedder.useConfiguration(configuration());
embedder.useCandidateSteps(candidateSteps());
embedder.useStepsFactory(stepsFactory());
This had some unexpected side effects for me. For example I am
logging which steps are being used. Since I call
configuredEmbeder() multiple times, the method stepsFactory() is
called multiple times. Even if I use just one instance of embedder
it is called many times since the JBehave framework calls
configuredEmbedder() many times.
Maybe it wold be good if there is another method added to
org.jbehave.core.ConfigurableEmbedder called "configureEmbedder"
which actually configures the embedder every time when it is called.
But the method "configuredEmbedder" should maybe be implemented
with lazy initialization, so that the calls in its method are just
executed once.
What do you think about it?
