[
https://issues.jboss.org/browse/SEAMFACES-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ken Finnigan updated SEAMFACES-222:
-----------------------------------
Forum Reference: https://community.jboss.org/thread/178884 (was:
http://seamframework.org/Community/BeanManagerUnavailableException)
> Support Portlet deployments
> ---------------------------
>
> Key: SEAMFACES-222
> URL: https://issues.jboss.org/browse/SEAMFACES-222
> Project: Seam Faces
> Issue Type: Feature Request
> Components: CDI Integration
> Affects Versions: 3.1.0.Beta4
> Reporter: Ken Finnigan
> Assignee: Ken Finnigan
>
> Currently Faces assumes that a ServletContext will always be available to
> retrieve a BeanManager, amongst other things. Support needs to be added for
> retrieving the BeanManager from a PortalContext when running inside a Portal
> environment.
> https://github.com/seam/faces/blob/develop/impl/src/main/java/org/jboss/seam/faces/beanManager/FacesServletContextBeanManagerProvider.java
> and
> https://github.com/seam/faces/blob/develop/impl/src/main/java/org/jboss/seam/faces/beanManager/BeanManagerServletContextListener.java
> definitely need Portal equivalents, and additional code could require
> updates but need to search for ServletContext to confirm.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.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
