pageflow <end-conversation> vs. @converstational

[asiandub]

hello,

[sorry for no formatting, i just keep on getting stupid errormessages telling me that i cannot have < p a g e > in my posting. removed it, but nothing changed.]

i have a problem understanding the following behaviour of seam.

(1) I have a pageflow in a long running conversation, associated with a controller in conversation scope. The controller is annotated with @Conversational

(2) The pageflow has - as the very last page - a confirmation page

     <page name="finishDeactivation" view-id="/x/y/z.xhtml">
          <end-conversation />
          <redirect />
     </page>
     
(3) The confirmation page is accessing a controller field with an EL expression #{controller.field.name}

What happens is that I get an exception as long as the controller is annotated with @Conversational. If I remove the annotation, everything works fine.

My interpretation is that

     <page name="finishDeactivation" view-id="/x/y/z.xhtml">
          <end-conversation />
          <redirect />
     </page>

ends the conversation before the page gets rendered.

I don't understand why.

Furthermore, if I remove the annotation, (but not the <end-conversation /> tag, I still have access to the correctly initialized field in the controller. Why's that? I would expect that a finished conversation would result in a fresh instance of the controller.

Hope someone can clarify...

Many thanks,
Jan

[asiandub]

ooops, just bumped into that question again ;-)

nobody able to clarify?

question was:

when does

<page name="finishDeactivation" view-id="/x/y/z.xhtml">
  <end-conversation />
  <redirect />
</page>


finish a conversation? is it a bug or a feature that i cannot access the conversation scope from inside x/y/z.xhtml anymore?

many thanks for clarifying,
jan

[schlegel]

Hi

What I know @Conversational means that every method invocation must be within a long running conversation.
But you end the conversation before the redirect to the finishDeactivation page.

[asiandub]

hello Hans,

thanks for answering. :-)

well, i don't know what you exactly are referring to with 'But you end the conversation before the redirect'.

What I want is ending the conversation on the last page. That's why I close it on the last page. don't be confused by the fact that ...end-conversation... comes before ...redirect.... this is due to dtd-restrictions and not up to my choice..

again - i would expect that ...end-conversation... ends the conversation after the view-id is rendered. but it seems to end the conversation as soon as it starts rendering the page.

unless someone has a good reason to do so, i would consider that this is a bug...

jan

[schlegel]

Hi Jan

end-conversation has two parameters - you could try this...

<end-conversation before-redirect="false"/>

I'm not sure what the default is...

hans

[asiandub]

this was it...

Danke!