Does seam pojo component support long running conversations?

[milli]

From the document I see the seam pojo component is stateful and has the default conversation scope. It also supports long running conversation. But it does not work for me. Is my understanding wrong or am I doing something wrong in my code? Any help is appreciated.

@Name("transactionPage")
public class TransactionPage extends AbstractPage {
......
@Create
public void initialize() {
 log.debug("************transactionPage created*****************");
}

@Begin
public String initiatePayment {
....
return null;
}

public String confirmDetails {
.....
return null;
}

@End
public String confirmed {
....
return null;
}
}

I have transaction.xhtml calling actions initiatePayment, confirmDetails and confirmed after every step.

What I notice is the method initialize(included for debuggin) is called everytime and resetting all the state stored from previous step. In a long running conversation I believe it should be called only once.

Thanks

[matt.drees]

Seam pojo components are actually event-scoped by default, not conversation-scoped.

[milli]

It is weird. In the seam book by Michael Yuan, it is mentioned in several places that a seam POJO component has conversational scope by default. I just checked the reference guide and it says event context.

Anyways I set the scope annotation to conversation explicitly but still have the same behavior.

BTW I'm using Seam 1.2.1GA and JBoss AS 4.0.5

[milli]

I just googled and found this is the behaviour of seam pojo component. http://chiralsoftware.com/Blog and they can not be part of a long running conversation.

Could someone please confirm this?

Thanks

[matt.drees]

Not at all true. I use conversation-scoped javabeans all the time.

[milli]

I think returning null was causing the problem. I thought returning null would take you to the same view and it does but it breaks the long running conversation. Now after returning the view id, it works I guess but still have to run some tests.

Thanks

[matt.drees]

Right; the docs say that @Begin only starts a long-running conversation if the (non-void return-type) method returns a non-null value.