Abhi Venu wrote: Now i have another utility class My doubt is what is wrong with calling session bean clas like this i.e treating it as a class
FacadeTestBean sessionBeanObj = new FacadeTestBean();
and calling its method
Please point out the pitfalls in it
This is calling Java code. It is not calling it as a session bean. As a result you don't get any of the benefits of using a session bean. No transactions. No security. No benefits over a Java class. In other words, there is no point in pretending it is an EJB if it is called as a POJO.