-
1. Re: @Out with stateless beans should be outlawed?
flashguru Jun 3, 2007 11:22 PM (in response to flashguru)Actually, it would be great if the @Out attributes are nulled after method invocations for stateless session beans. Should I open a JIRA issue for this feature?
-
2. Re: @Out with stateless beans should be outlawed?
gavin.king Jun 4, 2007 1:12 PM (in response to flashguru)Interesting point. Sure, open a JIRA issue and I will give it some thought.
-
3. Re: @Out with stateless beans should be outlawed?
flashguru Jun 4, 2007 7:43 PM (in response to flashguru)Great!
I just created a JIRA issue:
http://jira.jboss.org/jira/browse/JBSEAM-1394
Thanks -
4. Re: @Out with stateless beans should be outlawed?
flashguru Jun 4, 2007 8:26 PM (in response to flashguru)@RequestParameter has the same concern as the @Out
-
5. Re: @Out with stateless beans should be outlawed?
flashguru Jun 4, 2007 8:33 PM (in response to flashguru)"flashguru" wrote:
@RequestParameter has the same concern as the @Out
I take that back. @RequestParameter attributes do not have the same concern, simply because they are always injected with null values when their associated request parameters do not exist. -
6. Re: @Out with stateless beans should be outlawed?
supernovasoftware.com Jun 5, 2007 11:42 AM (in response to flashguru)I came across this problem quite some time ago.
It is quite confusing until you determine what is going on. -
7. Re: @Out with stateless beans should be outlawed?
liudan2005 Jun 5, 2007 9:11 PM (in response to flashguru)I have a similar problem with @Out and I don't know if it's caused by the same problem as described.
I have a page that dispalys a search box and serach result, when searchResult annotated with @Out is null, a search box shows. Otherwise, search result is displayed. I've noticed search result is not nulled even it's defined as stateless. I was looking for a way to nullify @Out annotated value once page is rendered, but couldn't find a way to do it. Looks like it's the same problem as flashguru described.