First off, it looks like you are using the old org.jboss.jsfunit.facade.JSFClientSession. The whole facade package will be removed for GA. It was only left in Beta 3 to allow Beta 2 users to migrate to the new org.jboss.jsfunit.jsfsession package, which uses HtmlUnit instead of HttpUnit.
Are you using Seam? It looks like you are using JBossEL or some other EL extension that allows params to be sent to a MethodExpression. So using the old facade package would keep Seam from getting initialized properly.
Yes using Seam.
I downloaded the latest builds from Hudson and installed them locally, do they contain the old Facade classes?
Was a bit confused about this because other posts in the forum had the ClientFacade classes, figured they'd been renamed :)
Should the new facades be in the jsfunit-core jar?
I have that and the seam and analysis jars in my local repo.
If I use the jboss snapshot repo, should I be able to get the latest snapshots? Or should I use nightly builds?
Right now, JSFUnit includes both packages, but the facade package will go away for GA.
So for now you have both:
But you should only use org.jboss.jsfunit.jsfsession.JSFClientSession. Also, you should no longer use the Seam jar. Seam support is built into JSFUnit core as long as you are using the jsfsession package.
We don't have nightly snapshots set up for JSFUnit yet. So if you want the very latest you will need to build it yourself from SVN. Since you are using Seam this might be a good idea because there have been a few Seam-related fixes since Beta 3.
Modifed the test to use the classes in the jsfsession package.
Not using a local build yet, waiting for the repo to get added to artifactory.
The test still fails, and the system.out.println statements are as follows:
Two different instances of the backing bean, do you know why this is?
Are there issues with working with non-long-running Seam conversations?
As I understand it, the instances of the backing bean won't always be the same from request to request. A Seam conversation is torn down and restored between requests, so what you seen in the System.out messages is probably correct.
Without more information, I have no way to tell why your assertion is failing. Perhaps "person" is not set correctly?
Here are the Seam bugs that have been fixed after Beta 3. I don't know of any other Seam issues:
when just using the page in the browser it works just fine.
I'll keep trying this and post here what I find.