How to deal with jsf caching of managed bean data?

Lets say I have a menu with 5 links in it.

I clicked link 1 that displayed a form, I filled up a form then submitted it. In the same page, a message in the screen that says "New Member was successfully added" was displayed.

I clicked link 2 that shows another module, then I click link1 again, but my problem is the message "New Member was successfully added" was still there. How do I go about erasing that message? Do I need to have a hold of that managed bean then erase that bean from context? LIke this

FacesContext context = FacesContext.getCurrentInstance();

context.getExternalContext().getSessionMap().remove("managed bean in link 1");

Is there any other way?

[707 byte] By [pauster007a] at [2007-11-27 6:09:50]
# 1
Any suggestions guys?
pauster007a at 2007-7-12 17:14:23 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 2
Use a request scoped bean for request scoped data.
BalusCa at 2007-7-12 17:14:23 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 3
Thanks for that idea Balusc. What if I have a managed bean and there are times that it should be in the session scope or sometimes it should be in the request scope? How do I go about that?
pauster007a at 2007-7-12 17:14:23 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...
# 4
Use a session scoped bean for session scoped data.You can find in http://balusc.xs4all.nl/srv/dev-jep-com.html several ways how a request scoped bean can access another session scoped bean.
BalusCa at 2007-7-12 17:14:23 > top of Java-index,Enterprise & Remote Computing,Web Tier APIs...