I thought I'd seen a portlet scope, that is PortletSession.APPLICATION_SCOPE reservation in earlier seam documentations and wondered what has happened when the time came for it to be used.
I'd rather be "misusing" session with Seam annotations than doing it "by-the-book" without Seam support. IPC of JBoss Portal is quite compact solution - one of the best in my opinion - in it's simplicity but not a solution that can be used with other portal containers. Also there is that one-to-one relationship between portlets restriction. I hope that this scope will come as part of Seam although it's directly supported by JSF and causes tight coupling with portlet api since I don't think new contexts below conversation can plugged in just like that allowing them to be truly optional. Mimicking IPC with Seams remote JMS capability seems to be an option, but I see that it may change radically in the future. One hack that came into my mind is to make ExternalContext session dynamically selectable. This only shifts problems to other areas even when not needing instance spesific sessions, since somehow JSF needs to transfer the state over portlet's processAction to renderRequest. This may even be against JSF spec and it doesn't concern the Seam implementation. Note that it requires access to the JSF binaries. I wouldn't go this way myself all the way, but this could propably be used to some sort of prototyping due to the benefit gained from Seam annotations that avoid completely the use of ((javax.portlet.PortletRequest) getFacesContext().getExternalContext().getRequest()).getPortletSession(). Knowledge of how MyFaces PortletExternalContext works is needed. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3952296#3952296 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3952296 _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
