On 8/21/06, ziya guven <[EMAIL PROTECTED]> wrote:
Hi, I think shale will be more popular when a navigation security implement because many developer already develop their authentication and authorization and these are most important parts of the projects so with the help of the navigation security shale will be most popular framework. And i have a question how can i access managed beans from a filter in shale ?
Filters are executed before the servlet gains control ... which means before the JSF FacesServlet has had a chance to set up the FacesContext and such for a JSF request. Therefore, a filter won't be able to use the managed beans APIs to create new beans. It can, however, have access to any attributes that have already been created, using standard Servlet API techniques (request.getAttribute() for request scope, request.getSession().getAttribute() for session scope, etc.). Craig Thanks for your helps..
Craig McClanahan <[EMAIL PROTECTED]> wrote: On 8/20/06, Adrian Mitev wrote: > > Is there in the Shale's roadmap to add security features. There is a JIRA issue already open to collect input on this topic[1]. It makes a lot of sense to me for Shale to have functionality in this area ... but I'm really interested first in what kinds of problems people want to solve, so we make sure we're building the right stuff. Commenting on this JIRA issue, or having conversations hers, are both good ways to start talking about the problems such a feature should address ... then, we can figure out what kind of stuff to actually build to solve to address those requirements. What kinds of things would *you* like Shale to do in this area? -- > Seeing is believing > Craig [1] https://issues.apache.org/struts/browse/SHALE-149
