I have the following situation...
| 1. user logs in
| 2. user object is outjected
| 3. work is done
| 4. backend process updates user in database
| 5. bean notices user update and refreshed from database
|
|
| I need the refreshed user data to be outjected however it is not
|
|
| | public class LoginAction {
| | private UserEntity user;
| |
| | @Out(required=false, scope=ScopeType.SESSION)
| | public String getUser() {
| | return user;
| | }
| | }
| |
| | public class AnotherBean {
| | @In(required=false) @Out
| | private UserEntity user;
| |
| | public void method() {
| | // update user with current data and have it outjected to other
objects
| | user = em.find(UserEntity.class, user.getId());
| | }
| | }
| |
| | public class ThirdBean {
| | @In(required=false)
| | private UserEntity user;
| |
| | public void method() {
| | // do something with user
| | // however user contains the old data not the new data from the
database
| | }
| | }
| |
|
| Is this possible? Am I doing it wrong? I guess I can always go to the
database, but I kind of like the idea of using seam to manage this object.
|
| Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999585#3999585
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999585
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
