JBossDeveloper

So, back to the original topic: Any idea how to get conversations to survive through Tomahawk components? This is a major block for me right now. I'm very happy with some of the cool tricks I can do with Tomahawk, but it means that everything I do has to be Session scope and I can't do any fancy conversation stuff. I can live without conversations at this stage in my web app but as it gets more powerful I will want to be able to support them. Any quick-fix type ideas?

As it's a UICommand component adding

<s:conversationId/>

<f:param name="conversationId" value="#{conversation.id}"/>

Is there any information how seam append its conversationId (or whatever) to the link?

I had a look at the DataScroller and it simply create a HtmlCommandLink dynamically, so it uses a standard JSF component to render the link.
Don't see what tomahawk does wrong here.

However, I'll point you (the jboss seam team) to the org.apache.myfaces.custom.requestParameterProvider package which allows you to register a RequestParameterProvider.
The fields and values returned by the RequestParameterProvider are appended to each url then.
This will be done by wrapping the HttpServletResponse and overload encodeURL.

Embedding a s:link for f:param with conversationId does not work.