Do we write one model bean for every JSF UI page?

Question

First, Please excuse my minimal knowledge in JSF, I am just starting to crawl :)
Is my understanding about JSF that you will be writing one model bean class for every JSP page you have, CORRECT? (this is just my understanding, I may be wrong)
This will be getting hard for large application.
Ideal scenario: Say you have a JSP page A.jsp to associate an action reference you write a model bean class and have appropriate get method to return an Action object.
Can we write an Action class, separated from the model bean class. I tried to create 2 different packages and one which just had a simple model bean and the other package had a Action class. I was not able to get this working as it was bouncing back with a Method innovation/Illegal argument exceptions. I am very confused here is it a necessity to write the action method in model bean or can we separate it? If we can separate it can we package it in to different packages?
I may be confusing in explaining my questions but to put it black and white
A)
1 JSP Page (uses JSF components) = 1 model bean class (?)
or
B)
1..n JSP pages (uses JSF components) = 1 or may be 2 model bean class (?)
If B is possible how do we get the action classes towards this architecture and how can we get access to the various model bean objects in a single action class.
Sorry for my vagueness....
Thanks
Ram

Answer 1

In the particular case of your separate Action class,
you still need a getter method for it somewhere. I
find it easiest to include this getter in the same
model bean that contains the data, but it doesn't have
to be. Craig,
It seems to be the consensus that a getter is required, but I've had perfect luck registering a single Action class in the application scope:
<managed-bean>
  <managed-bean-name>fooAction</managed-bean-name>    
  <managed-bean-class>org.bar.FooAction</managed-bean-class>
  <managed-bean-scope>application</managed-bean-scope>
</managed-bean>And then referencing it directly:
<h:command_button commandName="foo" actionRef="fooAction"/>This feels more like the Struts approach to me, as there's a single instance available. (If I wanted thread saftey, however, I could declare it in the request scope instead). I use this approach when there's no data associated with the Action (like a LogoutAction).
Kito D. Mann