EJB Architecture

[sam98uele]

Need your Opinion if it is a good Idea.

I've created:

• ProductAdminService: Stateful Bean, because it is used by the user (Admin) to Create a Product and add all the related Marketing Questions, and we cannot save the product until all the marketing questions are completed and submitted. And so we save the product once the user has created and submitted all the marketing questions.
• ProductUserService: Stateless Bean, because it is used by the User (Standard) to get the product of the day
• QuestionnaireAdminService: Stateless Bean, because it is used by the User (Admin) to Inspect the questionnaires
• QuestionnaireResponseService Stateful Bean, because it is used by the User (Standard) to fill up the questionnaire, and so navigate around the sections "Marketing" and "Statistical"

Note that they are needed because we have "Stateless" and "Stateful" EJB.

[alessandriniluca]

I Agree with your decision. The only thing is about productUserService. Whad does the user see after have completed the questionnaire? if user who has already compiled and submitted (or canceled) the questionnaire see different things, maybe this one could be stateful, because depends on the specific user

[sam98uele]

@alessandriniluca ProductUserService is used by the user to retrieve and display the Product of the day (needed by the Web to display the homepage, and also the other users reviews). After compiling the questionnaire the user sees only the homepage, with the product of the day and the other users reviews. But he cannot compile anymore the questionnaire, so, a method is present to check if a response is already present in the DB: productQuestionnariePresent(Integer userId);, and if true the button to compile the questionnaire is not displayed.