Add support for activating beans based on the JSF project stage
---------------------------------------------------------------
Key: SEAMFACES-185
URL: https://issues.jboss.org/browse/SEAMFACES-185
Project: Seam Faces
Issue Type: Feature Request
Affects Versions: 3.0.2
Reporter: Christian Kaltepoth
Hey all,
I think it would be a great enhancement if Seam Faces could support activation
of beans only in specific JSF project stages. MyFaces CODI supports a similar
feature with the {{@ProjectStageActivated}} annotation.
Examples:
{code}
@ProductionStage
@ApplicationScoped
public class ProductionEntityManagerProducer {
...
}
@DevelopmentStage
@ApplicationScoped
public class DevelopmentEntityManagerProducer {
...
}
{code}
Another very interesting usecase would be to enable specific
interceptors/decorators only in development stage. This could be used for
debugging stuff that is only interesting during development.
I think this could be easily implenented using an CDI extension that vetos
beans that do not match the active project stage. The only problem I'm seeing
is that we will need the JSF project stage in an very early stage during
application startup (actually before JSF started up). This means that we would
have to determine the project stage JSF will use ourselves.
The JSF spec describes that the project stage can either be set with a servlet
context parameter or using JNDI. If the latter one is uses, we could simply do
a JNDI lookup in the extension. No problem here. If the developer uses a
servlet context parameter the situation will become more problematic, because
we will need a reference to the ServletContext in the extension.
What do you think of this feature? Would it be useful? Any further ideas for
the implementation?
--
This message is automatically generated by JIRA.
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
