June 2002
Intermediate to advanced
400 pages
7h 48m
English
Now that we've had a look at stateful components, I think we have a better understanding of when a component is not stateful, more commonly known as stateless.
To set a component that isn't stateful as stateless is simple. Make sure the accessor isStateless() returns true. Let's return to WOMappedRolloverTest and set both reusable components WOMappedRollover and WOArea as stateless:
public boolean isStateless() {
return true;
}
After this is completed build and run.
There should not to be any observable difference. So what's all the fuss about?
When a component is set to stateless, only one such component is created in every application. It is ...