[ 
http://jira.codehaus.org/browse/JBEHAVE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264470#action_264470
 ] 

Alex Soto Bueno commented on JBEHAVE-491:
-----------------------------------------

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.




> Add JBehave Spring Namespace support for easier configuration
> -------------------------------------------------------------
>
>                 Key: JBEHAVE-491
>                 URL: http://jira.codehaus.org/browse/JBEHAVE-491
>             Project: JBehave
>          Issue Type: New Feature
>          Components: Spring Support
>    Affects Versions: 3.x
>            Reporter: Alex Soto Bueno
>            Assignee: Mauro Talevi
>             Fix For: 3.4
>
>
> I have implemented an initial version, it is a clone of master branch of 
> jbehave project. My implementation is on 
> [email protected]:maggandalf/jbehave-core.git
> Configuring Embedder for working with Spring shall be:
> <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>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to