[
http://jira.codehaus.org/browse/JBEHAVE-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mauro Talevi updated JBEHAVE-349:
---------------------------------
Fix Version/s: 3.0.2
Assignee: Mauro Talevi
It's not simply the abstract class bean that it complains about, those are
cared for in the isNotAbstract() method (since 3.0.1), which assumes that the
context is able to determine the type of the bean. This is not always the
case.
In any case, a more generic solution is to wrap the bean instantiation to catch
the BeansException as you suggest.
> JBehave Spring doesn't work with abstract beans
> -----------------------------------------------
>
> Key: JBEHAVE-349
> URL: http://jira.codehaus.org/browse/JBEHAVE-349
> Project: JBehave
> Issue Type: Bug
> Components: Spring Support
> Affects Versions: 3.0.1
> Reporter: Tom Marsh
> Assignee: Mauro Talevi
> Priority: Critical
> Fix For: 3.0.2
>
> Attachments: [tmarsh]_Fixing_abstract_bean_error.patch
>
>
> If you use abstract beans the annotation processor blows up.
> I've included a patch. Its basically a try catch around the getBean step.
> Test data enhanced to recreate problem.
--
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
