Add JBehave Spring Namespace support for easier configuration

Hi Alex, thanks for the very good contribution. I've pulled it in master.

A couple of comments:

• wouldn't the schema be more appropriately called "jbehave" rather than "embedder"
• ditto when the registering of the bean definition parser

What is not quite clear is your goal, i.e. you want to provide a namespaced version of the normal spring configuration or to just allow the construction of the embedder.

It's be very useful if you could also provide a unit-level behaviour that clarified your intent. You could start from SpringAnnotationBuilderBehaviour as a based for you SpringNamespaceConfigurationBehaviour.

Yes I agree with you jbehave would be better than embedder in schema name. About registering bean definition <jbehave:embedder id="embedder"> maybe embedder is better because we are registering an embedder for running JBehave with Spring.

For now my first goal is allow the construction of the EmbedderClassLoader using namespaces so less configuration is required, and for final users will be easier. But of course my idea is continue improving this integration.

For now I only want that user instead of writing:

<bean class="org.jbehave.core.io.LoadFromClasspath">

<constructor-arg>

<bean class="org.jbehave.core.embedder.EmbedderClassLoader">

<constructor-arg>

<list>

<value>target/classes</value>

</list>

</constructor-arg>

</bean>

</constructor-arg>

</bean>

<bean class="org.jbehave.core.parsers.RegexPrefixCapturingPatternParser">

<constructor-arg value="$" />

</bean>

<bean class="org.jbehave.core.configuration.spring.SpringStoryControls">

<property name="dryRun" value="false" />

<property name="skipScenariosAfterFailure" value="false" />

</bean>

<bean

class="org.jbehave.core.configuration.spring.SpringStoryReporterBuilder"

init-method="withDefaultFormats">

<property name="formats">

<list>

<value>CONSOLE</value>

<value>TXT</value>

<value>HTML</value>

<value>XML</value>

</list>

</property>

</bean>

could write

<jbehave:embedder id="embedder">

<jbehave:classpathLoader>target/classes</jbehave:classpathLoader>

<jbehave:output>TXT</jbehave:output>

<jbehave:output>HTML</jbehave:output>

<jbehave:output>CONSOLE</jbehave:output>

</jbehave:embedder>

but as I have explained my idea is adding more features, I am open to ideas of course.

About "It's be very useful if you could also provide a unit-level behaviour that clarified your intent. You could start from SpringAnnotationBuilderBehaviour as a based for you SpringNamespaceConfigurationBehaviour." sorry but I don't understand exactly what you mean.

Yes, I agree, but that is not what I meant. I've pushed some minor renames. The schema is now called jbehave-spring-1.0.xsd and lives in url http://jbehave.org/schemas/spring. Within the same schema we can define multiple elements, Embedder being one of them.

And if you could add a unit test that tests all this it would help to test the schema in isolation and communicate better the intend of what you've developed.

I've made a start on unit test with NamespaceHandlerBehaviour.

The syntax above seems to suggest that an Embedder instance is created, not just a LoadFromClasspath loader.

IMO, we should have all configuration beans supported by the schema, else it'd be confusing.

Moved to jbehave-spring-namespace branch until ready for release.