help us understand why can't you use action tag in pages.xml? This is exactly what you wanted right? Read database before you render(load) a page.

There are a few ways to do what you are trying to do.

An action will execute on each request so this will provide exactly the hook you need to do something like loading data. You can also fine-tune whether to execute this only on initial requests or only on post backs if needed. If you want to only reload certain entities and keep others, I think you could do an entityManager.refresh() on the entity you would reloaded. entityManager.clear() will detach all the entities but that's not the same as clearing out everything stored in the session...it all depends on how you have your entityManager set up (what scope, etc. it's stored in).

Another method that might be better suited to what you are trying to do is create a @Factory and scope it to request scope. A factory method can be used to automatically create (or load) objects into a scope.

Hope this helps.

It looks to me from what you posted that your page action fired off like it is supposed to but that your entityManager and/or entities are not in the state that you think they are in. So first thing I would recommend is putting in a debug statement at the beginning of your action to see if it fired off, then you can work on figuring out how to handle the entityManager.

There are lots of ways to set up and handle entityManagers, and if it's not done right you'll get exceptions like what you posted above. For example, if the entityManager is stored in the wrong scope or closes between requests, then your entities will be detached when you access them on a subsequent request and you'll get that LazyInitializationException.

The way I handled this was to let Seam manager the entityManager and just use @In to inject it in my beans and set it to manual flush mode also. Seam then stores the entityManager in conversation scope and also won't automatically close it...which means you can keep accessing it across several requests.

It's pretty complex to learn all the ins and outs but hopefully this will at least give you some place to start.

You can also fine-tune whether to execute this only on initial requests or only on post backs if needed.

Can you please explain this. I have the same requirement bu when my dataTbale is sorted or filtered this action execute event is getting executed. Please help.

Brandon Simpson wrote on May 20, 2009 19:08:


There are a few ways to do what you are trying to do.

An action will execute on each request so this will provide exactly the hook you need to do something like loading data. You can also fine-tune whether to execute this only on initial requests or only on post backs if needed. If you want to only reload certain entities and keep others, I think you could do an entityManager.refresh() on the entity you would reloaded. entityManager.clear() will detach all the entities but that's not the same as clearing out everything stored in the session...it all depends on how you have your entityManager set up (what scope, etc. it's stored in).

Another method that might be better suited to what you are trying to do is create a @Factory and scope it to request scope. A factory method can be used to automatically create (or load) objects into a scope.

Hope this helps.

Click HELP for text formatting instructions. Then edit this text and check the preview.

What is the scope of your persistence managers(components.xml)?
What scope is the data retrieved from the database stored(In action class)?
Do you have any extended conversation?

Show us your method in action class, components.xml, xhtml file, pages.xml or corresponding *.page.xml

I believe Brandon meant this.

<action execute="#{actionClass.method}" on-postback="false" />

This action is not executed on postback. Hope this helps.