aspose file tools*
The moose likes JSF and the fly likes Data issues on a SessionScoped managedbean JSF 2 Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » JSF
Bookmark "Data issues on a SessionScoped managedbean JSF 2" Watch "Data issues on a SessionScoped managedbean JSF 2" New topic
Author

Data issues on a SessionScoped managedbean JSF 2

C Bell
Greenhorn

Joined: Jun 29, 2009
Posts: 7
Deployment System: JSF 2.0.1.FCS Mojarra Implematation on Weblogic 10.3 appserver
No Spring or Hibernate.

Synopsis:
I have a table screen where a user can click an action (ie. edit, view) link on each row of data.
1. The user clicks a link on the table and receives a page (page 1) of information.
2. The user clicks an action on page 1, the user is then directed to the next page. On this page (page 2) there is no information.

If the user was to navigate back the table page and re-execute the previous actions the issue is resolved and there is no lose of bean information.
Both page 1 and page 2 contain the same managed bean (myBean).

Managed Bean info:
Name: myBean
Scope: Session

I have been on this issue for a few weeks, if anyone can assist please do.
If it helps, I always modify the request scope map before I return my actionString. I put an updated (from DB) myBean in this map.


Thank you in advance
Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16145
    
  21

Welcome to the javaRanch, "C"!

As a general rule, I always say that if you have any JSF imports in your source other than the JSF model classes, you're probably going about things the wrong way.

I can't really tell what you're about there, but it sort of looks like you're trying to stretch a domain model object to be a backing bean. Domain objects can be used as backing beans, but they tend to limit you, so it's often better to front the domain object with a domain-independent facade or decorator and use that as the backing bean, instead.

You shouldn't normally have any need to replace the backing bean - if it's transitory, a request scope object works better, and if it can't be transitory, it should have a way of being wiped clean and reused. I usually write an init() method to do that.


Customer surveys are for companies who didn't pay proper attention to begin with.
Kathiresan Chinna
Ranch Hand

Joined: Aug 17, 2008
Posts: 115
C Bell wrote:Deployment System: JSF 2.0.1.FCS Mojarra Implematation on Weblogic 10.3 appserver
No Spring or Hibernate.

Synopsis:
I have a table screen where a user can click an action (ie. edit, view) link on each row of data.
1. The user clicks a link on the table and receives a page (page 1) of information.
2. The user clicks an action on page 1, the user is then directed to the next page. On this page (page 2) there is no information.

If the user was to navigate back the table page and re-execute the previous actions the issue is resolved and there is no lose of bean information.
Both page 1 and page 2 contain the same managed bean (myBean).

Managed Bean info:
Name: myBean
Scope: Session

I have been on this issue for a few weeks, if anyone can assist please do.
If it helps, I always modify the request scope map before I return my actionString. I put an updated (from DB) myBean in this map.


Thank you in advance


Hi Guys,

Is JSF 2.0 workin gin Weblogic 10.3 server ? I had an issue about 'WeblogicInjectionProvider'.
Could you tell any workaround about this ?

Thanks
Kathiresan

Tim Holloway
Saloon Keeper

Joined: Jun 25, 2001
Posts: 16145
    
  21

Kathiresan Chinna wrote:
C Bell wrote:Deployment System: JSF 2.0.1.FCS Mojarra Implematation on Weblogic 10.3 appserver
No Spring or Hibernate.

Synopsis:
I have a table screen where a user can click an action (ie. edit, view) link on each row of data.
1. The user clicks a link on the table and receives a page (page 1) of information.
2. The user clicks an action on page 1, the user is then directed to the next page. On this page (page 2) there is no information.

If the user was to navigate back the table page and re-execute the previous actions the issue is resolved and there is no lose of bean information.
Both page 1 and page 2 contain the same managed bean (myBean).

Managed Bean info:
Name: myBean
Scope: Session

I have been on this issue for a few weeks, if anyone can assist please do.
If it helps, I always modify the request scope map before I return my actionString. I put an updated (from DB) myBean in this map.


Thank you in advance


Hi Guys,

Is JSF 2.0 workin gin Weblogic 10.3 server ? I had an issue about 'WeblogicInjectionProvider'.
Could you tell any workaround about this ?

Thanks
Kathiresan



Kathiresan, please don't hijack the thread. It does you a disservice because not everyone using WebLogic may read this thread, so someone who knows the answer might not realize you'd asked the question. If you'd started a new thread with your question as the subject, you'd get more answers. Plus, when a thread gets split into 2 unrelated conversations, it confuses people.

Actually, because only WebLogic is involved, you'd probably get a better set of answers if you asked this in the WebLogic forum, even though you're asking about JSF.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Data issues on a SessionScoped managedbean JSF 2