Where the @NoneScoped can be applied?
posted 4 years ago
About a good utilization the @NoneScoped, I have seen some developers saying that it is good to put the converter as a ManagedBean, to be able to do Injections.
Is NoneScoped a good scope to use in the Converters to allow the injection?
I saw in this post (http://stackoverflow.com/questions/3086896/what-is-none-scope-bean-and-when-to-use-it) that this scope would be good when used to read faces-config parameters.
Is NoneScoped a good scope to use in the Converters to allow the injection?
I saw in this post (http://stackoverflow.com/questions/3086896/what-is-none-scope-bean-and-when-to-use-it) that this scope would be good when used to read faces-config parameters.
posted 4 years ago
I'd forgotten there even was such a thing!
The URL you referenced seems to have a good explanation. If you are coding EL and you need the EL to reference a "throwaway" bean that exists only for the duration that that particular EL expression is being evaluated, NoneScoped would be suitable. Not that I've ever needed to do that, but it would allow you to offload complex computations and other data manipulations into Java code instead of doing them in EL - which is both potentially an MVC violation and definitely a
to debug,
From that usage, I think I could consider them as a UI equivalent to Session EJBs, only something between stateless and stateful; stateful EJBs would retain scope between uses, whereas the NoneScoped beans would simply be discarded.
The URL you referenced seems to have a good explanation. If you are coding EL and you need the EL to reference a "throwaway" bean that exists only for the duration that that particular EL expression is being evaluated, NoneScoped would be suitable. Not that I've ever needed to do that, but it would allow you to offload complex computations and other data manipulations into Java code instead of doing them in EL - which is both potentially an MVC violation and definitely a
to debug,
From that usage, I think I could consider them as a UI equivalent to Session EJBs, only something between stateless and stateful; stateful EJBs would retain scope between uses, whereas the NoneScoped beans would simply be discarded.
An IDE is no substitute for an Intelligent Developer.
posted 4 years ago
I do think as you, but do you think that would be a good usage to a converter as NoneScoped? Instead the RequestScoped?Tim Holloway wrote:I'd forgotten there even was such a thing!
The URL you referenced seems to have a good explanation. If you are coding EL and you need the EL to reference a "throwaway" bean that exists only for the duration that that particular EL expression is being evaluated, NoneScoped would be suitable. Not that I've ever needed to do that, but it would allow you to offload complex computations and other data manipulations into Java code instead of doing them in EL - which is both potentially an MVC violation and definitely a
From that usage, I think I could consider them as a UI equivalent to Session EJBs, only something between stateless and stateful; stateful EJBs would retain scope between uses, whereas the NoneScoped beans would simply be discarded.
| Did you see how Paul cut 87% off of his electric heat bill with 82 watts of micro heaters? |