[
https://jira.jboss.org/browse/SEAMSERVLET-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12536350#action_12536350
]
Lincoln Baxter III commented on SEAMSERVLET-7:
----------------------------------------------
Thanks, Stuart. I'm assuming that the problem here would be that we're assuming
there's only one servlet context in which to set the BeanManager? Thus, others
get "forgotten" or overwritten due to the fact that there's only room for one
in this producer's internal state? Makes sense. Good catch!
> ServletContextProducer assumes there is only one ServletContext
> ---------------------------------------------------------------
>
> Key: SEAMSERVLET-7
> URL: https://jira.jboss.org/browse/SEAMSERVLET-7
> Project: Seam Servlet
> Issue Type: Bug
> Reporter: Stuart Douglas
>
> But in a multi war setup there are 2 or more.
> This assumption was actually the root cause of all the multi war bugs in seam
> 2, so it will definitely cause problems down the track.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
