The way I handle using the scenario name is to provide a Spring bean (effectively a singleton that is created at system startup). The BeforeScenario annotated method calls a method on the bean to store the current scenario name, and provides a method to use this name later.
It's not an ideal solution, but it suffices for my needs. Rob *********************************************************************************** This e-mail and attachments are intended for the above name only and may be confidential. If they have come to you in error, you must take no action based on them, nor must copy or show them to anyone; please reply to this e-mail and report the error. Security warning: Please note that this e-mail has been created in the knowledge that the internet is not a one hundred percent secure communication medium. We advise that you understand and observe this lack of security when e-mailing us. Virus: Although we have taken steps to ensure that this e-mail and attachments are free from any virus, we advise that in keeping with good practice the recipient should ensure they are actually virus free. If you have received this e-mail in error please notify: [email protected] YELL ADWORKS is a business name of YELL MEDIAWORKS LIMITED Registered Office: Queens Walk, Oxford road, Reading, Berkshire, England, RG1 7PT. Registered in England and Wales, registered number 06649631 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
