[JBoss JIRA] Created: (SEAMFACES-50) Extra BeanManagerProviders in service file results in no BM found on beta-1
by Nicklas Karlsson (JIRA)
Extra BeanManagerProviders in service file results in no BM found on beta-1
---------------------------------------------------------------------------
Key: SEAMFACES-50
URL: https://jira.jboss.org/browse/SEAMFACES-50
Project: Seam Faces
Issue Type: Bug
Components: Build & Distribution
Affects Versions: 3.0.0.Alpha3
Reporter: Nicklas Karlsson
The faces modules contains the service file for BeanManagerProvider that has
org.jboss.weld.extensions.beanManager.DefaultJndiBeanManagerProvider
org.jboss.weld.extensions.beanManager.JBossJndiBeanManagerProvider
in addition to it's own
org.jboss.seam.faces.beanManager.FacesServletContextBeanManagerProvider
Since the weld extensions also carry the Default/JBoss JNDI providers we end up with 5 providers for that dependency combination. For some reason (classloading?), in the beta1-AS Pete provided this is a problem - resulting in *no* BeanManagers being found (which results in a crash when the faces module SeamExternalContext is set up for the first time)
Removing the JNDI based BeanManagerProviders from faces appears to help the issue itself but it leaves the faces module completely dependent on other modules for BM access
--
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
14 years, 7 months
[JBoss JIRA] Created: (SEAMSECURITY-12) Introduce session management into Seam Security
by Shane Bryzak (JIRA)
Introduce session management into Seam Security
-----------------------------------------------
Key: SEAMSECURITY-12
URL: https://jira.jboss.org/browse/SEAMSECURITY-12
Project: Seam Security
Issue Type: Feature Request
Reporter: Shane Bryzak
Assignee: Shane Bryzak
Fix For: 3.0.0.Beta1
A feature in which many of our users have expressed interest in the past, session management would provide an application-scoped registry of all active user sessions. We should provide features for terminating selected user sessions, setting a policy for multiple user sessions (one/multiple session per user) and provide some kind of formal support for session logging (last login time, ip address, etc). Up till now we've told our users to implement all this stuff manually, but I think it would be cool if we provided support for it out of the box.
--
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
14 years, 7 months