Design Question using EJB3.0

[PavanPL KalyanK]

This is my servlet

public class Servlet2Stateless
  extends HttpServlet 
{
    @EJB
    private StatelessSession sless;
           out..println(sless.sayHello(val)
            }

This is my Remote interface

public interface StatelessSession {
    public String sayHello(String name);
}

This is my SessionBean class where i directly implemented the logic

@Stateless
public class StatelessSessionBean
    implements StatelessSession {

    public String sayHello(String name) {
        return "Hello”;

    }

Now my question is it a good pratice to directly implement the logic inside the SessionBean .

I want to ask what is the general approach followed where we need to contact the DataBase for some operations .Please help.

waiting for your suggestions.

[PavanPL KalyanK]

Is my question vague ??

[Reza Rahman]

Pavan,

This is a question that most EJB 3/Java EE 5 references cover in detail (EJB 3 in Action certainly does). As a brief summary, the choice is really up to you. You can put business logic in session beans while using a separate DAO layer to encapsulate persistence code. This is the traditional Java EE layered architecture. If you wish, you can omit the DAO layer while using JPA. Some folks have argued that JPA makes the DAO layer obsolete. You can also use domain driven design (DDD) and put business logic in domain objects that are invoked by session beans.

Hope it helps,
Reza

[PavanPL KalyanK]

Reza , thanks for your excellent explanation