Migration from 1.2.1 to 2.0.0

[leowenttechie]

Hi
I am migrating my application and was going thorugh the steps in seam2Migratrion.txt . I am facing a small problem. I was using the API Manager.instance().getConversationIsLongRunningParameter() which is no more available. What should i do for that as what is the alternative?

[nickarls]

alok kumar wrote on Feb 20, 2008 08:34 AM:

What should i do for that as what is the alternative?

the static Conversation (or was that Conversations) instance has a isLongRunning()

[leowenttechie]

I am talking about, how to get the longrunning parameter which the before mentioned method gives... generally clr which we define in components.xml.
How to get that in the 2.0.0 release.

[gavin.king]

There is no longer any such parameter. It is no longer needed in Seam2.

[leowenttechie]

Hi Gavin,
Thanks for the quick reply. Can you please elaborate on that ? How does it work with Seam 2 whereever we were using this parameter earlier .

[nickarls]

section 30.9 in the 2.0.1.GA docs lists infra component

org.jboss.seam.core.manager.conversationIsLongRunningParameter

the request parameter used to propagate information about

whether the conversation is long-running, default to

conversationIsLongRunning.

What is this related to?

[leowenttechie]

I have created a HttpSession object from HttpServletRequest object using request.getSession().
But when i am cheking for Contexts.isSessionContextActive() ... i am getting it as false. Is there anything special i need to do for this ... with the 1.2.1 version the same code was working fine .

[leowenttechie]

I am sorry to bug so much on the forum but i don have an alternative. My application was using Seam 1.2.1 with JSF 1.2
Now that i am trying to move to Seam 2.0.0 i am getting a lot of runtime errors ( compilation problems i was able to resolve with the help of seam2Migration.txt)
Do we have a document which talks about this kind of migration in detail. that will be really helpful