[
http://jira.codehaus.org/browse/XFIRE-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154991#action_154991
]
Karl Palsson commented on XFIRE-724:
------------------------------------
Jsr181HandlerMapping also tries to create beans marked lazy-init="true"
> Jsr181HandlerMapping and scoped beans in Spring 2.0
> ---------------------------------------------------
>
> Key: XFIRE-724
> URL: http://jira.codehaus.org/browse/XFIRE-724
> Project: XFire
> Issue Type: Bug
> Components: Spring
> Affects Versions: 1.2.2
> Environment: XFire 1.2.2
> Spring 2.0
> Reporter: Radim Tlusty
> Assignee: Dan Diephouse
> Attachments: xfire-jsr181+session-scope.txt
>
>
> When Jsr181HandlerMapping class (in method method processBeans) scans bean
> factory for beans which have JSR 181 annotations, it grabs live instances of
> beans from bean factory (calls beanFactory.getBean(...).
> This causes problems for Spring 2.0 beans which has 'session' or 'request'
> scope, because they can be obtained only from context of HTTP request (see
> attached stack trace).
> Is it really necessary to get the live beans from the bean factory?
> I have locally patched it in following way
> -- bean target class name for bean I take from the BeanDefinition object
> -- the class object is obtained using Class.forName using bean factorie's
> class loader
> -- in this case I don't need the live bean instance
> such like: clazz = Class.forName(def.getBeanClassName(), false,
> ctxt.getClassLoader())
> But I'm not sure, if it's right.
--
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
