struts design

[Betsy Camel]

hi all
i am developing a application in which the user interface for 3 screens are the same but they have slightly different functionalities. is it a good idea to have the same action class and form bean for them

[suj hande]

I have one suggestion. If i were you before i decide i would consider

If this app going to be used for a short time and you are sure about the functionaliy or is this going to be used for long time.

If short time then what you say now is right.

If long time then you have to consider if you will be adding additional functionalities to individual screens as you go.
If yes then go for seperate so it will easier in future.

[Srini Kesavan]

While having them separate is easy for maintenance. It also introduces some redundancy.

Some things to consider:

Even for long run, there are advantages to have same action and form.

If there is some common processing logic that needs to be in the action class,
it need not be duplicated.

The same form can be used. If there are some additional fields are required for one page but not others.
It can be added to the form class. Other pages will not use them.

Also consider the general practice in your company. It pays to be consistent.

I hope you have enough information to make a decision now.