I'm looking at load testing my Seam App and I was wondering what was the easiest way to do this given conversations. I've had a look at Grinder and Jmeter so far but there doesn't seem to be any way to handle the conversation id parameter from request to request and keep it different for each simulated user.
Has anybody got any experience load testing seam apps and is prepared to make some recommendations?
We did with JMeter. Just capture the conversation id with a regular expression as you do with JSF View State.