Seam Stateless Beans

[fcorneli]

I have this @Stateless bean with a setName() and getName() and a process() method. The first time I call process() via the page all is OK, but the second time the page calls getName() first, which still contains the previous value. Is there a way to clean this besides doing?

public void process() {
 try {
 reallyProcess();
 }
 finally {
 this.name = null;
 }
}

I don't want to start a conversation for a single page. How does Seam handle the lifecycle of @Stateless beans?

[gavin.king]

Stateless session beans should NEVER have setter methods! Use a stateful bean (and read up on the definition of "stateless" in EJB).

[fcorneli]

I thought Seam was somehow managing that a single JSF lifecycle always got to see the same stateless bean instance. Apparently I'm using the wrong Maven2/Facelets port of the dvdstore to learn all about Seam... http://vyzivus.host.sk/site-files/dvdstore.zip

[gavin.king]

I thought Seam was somehow managing that a single JSF lifecycle always got to see the same stateless bean instance

Definitely not. Seam can't magically make a stateless bean stateful.