s:link page parameters and performance

[dustismo]

I have been doing most of the navigation of my site using s:link and page parameters. Now I am doing profiling and realize that every page parameter is evaluated in its backing bean! Ack.. So for every s:link I use; the backing bean is created and the params evaluated (so basically EVERY bean in my app is created for every page).. How can I get around this? I need to continue to use page parameters but this performance is unacceptable. It would seem that the whole bookmarkable url scheme is inherently flawed, or am I missing something?

thanks,
Dustin

[dustismo]

Huh, no responses? How is everyone else handling navigation? I have been trying to find away around using page parameters but I can't find an elegant solution.

Without any content my page takes 16 secs to load just because of all the s:link page params getting evaluated.

[christian.bauer]

16 seconds to evaluate maybe three or four page parameters (i.e. three or four method calls)? If you want to know what you are doing wrong, you need to post some code.

[dustismo]

Thanks for the response. I guess I wasn't very clear in my initial description. The site is very large and every page has many many links on it (i.e. ebay, amazon, ect..).. And almost every single page in the site has some page page parameters and a backing bean. Thus on every single page load ALL of the bean are built in order evaluate the params. So there are literally hundreds of parameters that are being evaluated.

I can switch many of links them to be simple hrefs pointing to the .seam, but I don't like having to keep track of the conversations by hand, and then I cant use propagation=nest and such.

Does that make more sense?

Any suggestions would be appreciated.
-Dustin

[christian.bauer]

Actually, I still have no clear idea what you are trying to do. Code?