I would post code but....there's just way to much of it :P
But, if you end up needing some, I'll see if i can write a smaller test (although I'm running a little short of time :P)
What do you mean by conversation? Do you mean that you are losing the Http Session or are you talking about a Seam conversation?
Sorry, I should have clarified.
It is a SEAM conversation. (The app I'm writing is running SEAM so...I'm almost always going to mean SEAM :) )
So yes, I have an @Out(jected) variable that is now null because my conversation is lost.
Hope that makes more sense now :)
Have you tried the SeamClient? It extends JSFClientSession.
Yeah, I tried the SeamClient but I had exactly the same result.
I'm at a bit of a roadblock now, I'm not sure how to proceed with testing if I can't get this to work....
I might have to just do a straight navigate to page...I'd rather not do that though.
I hope we can work out what's going on. If I get a spare 5 mins I'll try write up a much smaller test so I can post my code.