[
http://jira.codehaus.org/browse/JBEHAVE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192568#action_192568
]
Mauro Talevi commented on JBEHAVE-150:
--------------------------------------
JBehave is designed to be component-oriented with clear
interface-implementation separation.
For the case at hand we'd need to provide an implementation of the
ScenarioDefiner interface. You can start from the ClasspathScenarioDefiner as
a guideline for the URLScenarioDefiner. Also you should look at the
ScenarioFileLoaderBehaviour (which should be renamed to
ClasspathScenarioDefinerBehaviour).
Any questions, just post it on the mailing list and we'll help you.
Thanks
> URL-based scenario definer
> --------------------------
>
> Key: JBEHAVE-150
> URL: http://jira.codehaus.org/browse/JBEHAVE-150
> Project: JBehave
> Issue Type: New Feature
> Components: Core
> Reporter: Mauro Talevi
>
> As a scenario developer, I want to access scenarios definable via URLs, not
> necessarily in the classpath.
> This can be used, e.g. to retrieve scenarios from wikis.
--
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
