JBossDeveloper

Sorry for not beeing specific.

To start all over. I have a seam component called mainAdministration. This component is conversational in nature. It uses many methods which start a different pageflows. One particular pageflow is called "newObject". This page flow is started by SEAM component "mainAdministration with method newObject.

@Name(ContextVariables.MAIN_ADMINISTRATION)
@Scope(ScopeType.CONVERSATION)
public class MainAdministration {

...
 @Begin(join=true,pageflow="newObject")
 public String newObject() {
 return NavigationOutcomes.BROWSE;
 }
...
}

<pageflow-definition name="newObject">
 <start-state name="start">
 <transition name="browse" to="selectClass"></transition>
 </start-state>
 <page name="selectClass" view-id="/selectClass.jsp" redirect="true" >
 <description>#{msg.title_selectClass}</description>
 <transition name="browse" to="selectClass"></transition>
 <transition name="cancel" to="mainAdministration"></transition>
 <transition name="select" to="editObject">
 <action expression="#{classSelection.selectClass}" />
 </transition>
 </page>
 <page name="editObject" view-id="/editObject.jsp" redirect="true">
 <description>#{msg.title_editObject} : #{objectType}</description>
 <event type="node-enter">
 <action expression="#{newObject.createObject}" />
 </event>
 <transition name="ok" to="mainAdministration">
 </transition>
 <transition name="cancel" to="mainAdministration">
 <action expression="#{newObject.removeObject}" />
 </transition>
 <transition name="back" to="selectClass">
 <action expression="#{newObject.removeObject}" />
 </transition>
 </page>
 <page name="mainAdministration" view-id="/mainAdministration.jsp" redirect="true">
 <end-conversation />
 </page>
</pageflow-definition>

<af:commandLink id="aPartner" text="#{msg.class_partner}" action="select">
 <f:param name="objectType" value="Partner" />
 </af:commandLink>

public void beforePhase(PhaseEvent event)
 {
 if ( event.getPhaseId() == RESTORE_VIEW )
 {
...
 }
 else if ( event.getPhaseId() == RENDER_RESPONSE )
 {
 callAction( event.getFacesContext() );
 Pages.instance().callAction();
...
 }
 }

 }

Now i think I find the source of the problem but not the answer. I by mistake though how navigation works. Actually this is the code that should invoke pageflow transitions.

Manager.instance().prepareBackswitch(event);

This is exactly why it does not work. By debuging I found out that conversation was not propagated. What is strange is that old distribution of SEAM did propagate conversation ID. Maybe this has some relevance that I use ADF Faces <af:commandLink ..> I wil try the same stuff and put <f:param name="conversationId" value="#{conversation.id}" /> just to see what happens .

OK here are my findings.

When I included <f:param name="conversationId" value="#{conversation.id}" /> command links start working. Now there was definitelly a change in the SEAM which now does not do conversation propagation at lieast for ADF Faces command buttons and links. I did not checked standard JSF components <h:commandLink... and <h:commandButton... Just to be sure I again reinstalled jboss-seam,jar from distribution of beta 2 and replaced this nightly build with the beta2 one. My ADF Faces command links and buttons did work.
I dont really want to use <f:param.

What was the change that ADF Faces command components do not propagate conversation id anymore? Currently I treat solution with <f:param as a workaround.

Silvo Koren

This is definitely a bug. I did checked also with <h:form> and <h:commandLink> and behaviour is the same. "IF YOU DO NOT PROVIDE CONVERSATION ID as parameter" conversation is not propagated.

Silvo Koren

Hello

Yes booking example works. But booking example does not uses pageflows. You shoul try dvd store example. This one is broken. I think this problem is bound to pageflows. Booking example has pages.xml defined so SeamPhaseListener is using this type of navigation and not pageflows.

Silvo Koren

I haver to correct myself.

DVD store demo was broken regarding some *.xhtml files. <h:form> tag was missing on some places and i puted it on also on wrong place.

DVD Store is working so I have to figure out what is different in our application. We do use a bunch of forms but DVD Store also has such scenario. Maybe this is issue regarding fillers and phaselisteners. I dont have source code for ADF Faces to check this out. What is still strange is that there was some change in SEAM which now does not work anymore. I will still try to figure this out.

Silvo Koren

New findings

When I running DVD Store example I allways go throught restoration twice. Conversation restoration happens on a second iteration. In our application restoration happens only one time. And this time conversationId is set to empty string. This is why I dont get conversation propagated. I suspect that no redirections takes place in our example. This is probably why on DVD Store example we have two restorations, because we had two requests. One for issuing action and one for redirection. In our example only one request happens. But I did have redirect set to true.

Silvo Koren

Hello

Here are my new findings. Previous implementation of conversation propagation used a folloving method on class Manager:

 public void restoreConversation(Map attributes, Map parameters)
 {

 //First, try to get the conversation id from a request parameter
 String storedConversationId = getConversationIdFromRequestParameter(parameters);

 if ( isMissing(storedConversationId) && attributes!=null )
 {
 //if it is not passed as a request parameter, try to get it from
 //the JSF component tree
 storedConversationId = (String) attributes.get(CONVERSATION_ID);
 }

 ...
 }

 public void restoreConversation(Map parameters)
 {

 //First, try to get the conversation id from a request parameter
 String storedConversationId = getConversationIdFromRequestParameter(parameters);

 if ( isMissing(storedConversationId) && Contexts.isPageContextActive() )
 {
 //if it is not passed as a request parameter, try to get it from
 //the JSF component tree
 //storedConversationId = (String) attributes.get(CONVERSATION_ID);
 storedConversationId = (String) Contexts.getPageContext().get(CONVERSATION_ID);
 }

 ...
 }