I believe I have hit a time of reverence and wisdom, and would like someone to
check my knowledge.
I think my largest problem, is in thinking that the object has to already be
instantiated, or at least defined BEFORE calling it from a Faces page:
I guess that's not the case. In the SessionBean, the object:
| @Stateless
| public class blah{
| @In @Out private User currentUser;
| @In private User assignedUser;
| @In private User ownerUser;
| }
|
Those objects aren't defined anywhere else. As long as the JSF page's action
submits to this SLSB, the objects are created (if need be) by this:
| <h:inputText value="#{currentUser.username}" />
| <h:inputText value="#{assignedUser.username}"/>
|
Is that correct?
And the @Out annotation can be used on the next page that's rendered.
So, if I'm correct, then here's my next question:
If the User Entity Bean is set to a SESSION context, does that mean my request
variables also eat up memory?
For example, only the currentUser variable should be stored in the SESSION.
But, since assignedUser and ownerUser are both objects of the User class,
which, in turn, is defined as a SESSION component, are those two objects also
stored in the SESSION, even though I'm only using them as REQUEST objects?
Thanks for helping me understand.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919237#3919237
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919237
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
