Pageflows with RESTful URLs

[smithbstl]

Has anyone tried using these two together? I can't seem to get parameters to propagate across redirects when in a pageflow. If I try to forgo the transition in the pageflow and point an s:link directly to the page using the view property, I get "Illegal Naviation" errors.

pageflow.jpdl.xml

<start-page name="addressSearch" view-id="/addresslookup.xhtml">
 <transition name="viewServiceRequests" to="serviceRequestListing">
 <action expression="#{addressLocator.viewServiceRequests}"/>
 </transition>
 <transition name="viewServiceRequest" to="serviceRequest"/>
</start-page>

<page name="serviceRequest" view-id="/servicerequest.xhtml"
 back="enabled">
 <redirect/>
 <transition name="viewAssignments" to="assignmentListing"/>
</page>

I get the same behavior even when I remove the redirect.

pages.xml

<page view-id="/servicerequest.xhtml">
 <param name="serviceRequestId" value="#{serviceRequestManager.serviceRequestId}"
 converterId="javax.faces.Long"/>
 <begin-conversation join="true"/>
 <action execute="#{serviceRequestManager.loadServiceRequest(serviceRequestManager.serviceRequestId)}"/>
</page>

This link is not propagating the serviceRequestId parameter, only the conversation id

<s:link action="viewServiceRequest"
 value="#{req.serviceRequestNumber}">
 <f:param name="serviceRequestId" value="#{req.serviceRequestId}" />
</s:link>

This link gives me an "Illegal Navigation" error message inserted into FacesMessages

<s:link view="/servicerequest.xhtml"
 value="#{req.serviceRequestNumber}">
 <f:param name="serviceRequestId" value="#{req.serviceRequestId}" />
</s:link>

What the heck am i doing wrong?

I am running Seam 2 CR1 with RichFaces 3.1.1 Snapshot from 9-24-2007

[pmuir]

I'm not sure that pageflows with restful urls make sense - a pageflow is by nature stateful and doesn't store its state in request parameters.

I'm guessing what you are trying to do is provide links which when bookmarked and revisited would kick the user back to the start of the pageflow?

[smithbstl]

Exactly. I can get state information to the user fine without page actions or any RESTful behavior. I just wanted the resulting page to be bookmarkable.

Its a master/detail type of search and would like the detail record/page to be able to be bookmarked.

[pmuir]

Please file a feature request for this, it's a reasonable request :)