Request parameters deleted after first submit

[bogdanmocanu2011]

Hello,

I am developing an application with Seam and for one page (a book view page) I specified that I need an id sent as a request parameter. So my URL must be /book-view.seam?bookid=22.

Everything is ok, from the book list page I get redirected to book-view, and the id is correctly set. However, after first change in the page (that is, after first submit of the page), Seam deletes the request parameter (all these submits from the book-view page happen in a conversation).

Now this is a problem for me. I would like the bookid request parameter to remain on that page, in order to keep the page bookmark-able.

Here is my configuration for the book-list:

<page view-id="/book-list.xhtml">
    <navigation from-action="#{bookSearch.selectBook}">
        <begin-conversation/>
        <redirect view-id="/book-view.xhtml">
            <param name="bookid" value="#{bookSearch.book.id}"/>
        </redirect>
    </navigation>
</page>

And here is the configuration for book-view:

<page view-id="/book-view.xhtml" no-conversation-view-id="/home.xhtml">
    <param name="bookid" value="#{bookView.bookIdStr}"/>
</page>

So my question is how can I make Seam to keep the request parameters on each redirect, so that they remain in the address bar after each submit from a page that requires these parameters?

Should I stop using <h:commandLink/> and <h:commandButton/> and instead use <s:link/> and <s:button/> ?

Thank you very much for reading this post, and for your answer in advance.

Bogdan.

[sjmenden]

See: http://docs.jboss.com/seam/2.0.3.CR1/reference/en-US/html_single/#d0e2121 for an example on a bookmarkable search page and see: http://docs.jboss.com/seam/2.0.3.CR1/reference/en-US/html_single/#d0e4475 for more detail on page params.

-Samuel

[bogdanmocanu2011]

Thank you Samuel for your answer.

Yes indeed, the links that you specified contain the answer to my question. I also found the following page that provides more information on page parameters, conversations and workspace management: http://docs.jboss.com/seam/latest/reference/en-US/html/conversations.html

The ideea is that when when you need a page to receive a parameter as a request parameter (through GET), then the best strategy is to use the PARAM tag in pages.xml. However, after you design that page to accept and use that parameter, there are some cases (as I had a few days ago, when I posted the first message) when I needed to directly generate some links to this page, links that contain the GET parameter. And to solve this problem, the most elegant solution is to use <f:param/> inside a <h:outputLink/>. Moreover, this way you can also propagate the conversationId parameter (not just the conversation itself) (or just keep the parameter in the address bar, since Seam has the bad behaviour of removing the conversationId from the address sent to the browser for redirection).

Bogdan.

[tienlantri]

Hi Bogdan,

I have the same problem as you even though I dont do bookmark like u. My purpose is to write only one xhtml page and one Action but it can be served to many objects (have the same type of attributes). That's why I need to use request parameter to distinguish the object in order to instantiate them correctly.

However, I cannot use <h:outputLink/> because I need to perform an action when I click on the link. That's why I use <a4j:commandLink/>

So do you have any idea to keep the parameter attached to the URL to the end (I mean after do several actions)?

Thanks,
Tina

[lvdberg]

Hi,

you can use the @in and @out annotations also to pass parameters between requests. Is better manageable and you keep the parametersclose to your code instead of inside a pages.xml file.

Leo