I would appreciate your suggestions and comments on the following design approach.
In our project we have decided to use Stateless Session EJBs with Containter Managed Transaction.
In our existing design the Bean Class extends a normal java class which contains all the business methods.
for example
My architect has been recommending this approach to sepearte business concerns from the actual ejb class. But i have been recommending not to adopt this design as we may loose some of the features provided by the EJB Container like SessionContext handling etc.
It would be great, if all of you could share your thoughts. Your suggestions would really help us to make a decision.
I would appreciate your suggestions and comments on the following design approach.
In our project we have decided to use Stateless Session EJBs with Containter Managed Transaction.
In our existing design the Bean Class extends a normal java class which contains all the business methods.
for example
My architect has been recommending this approach to sepearte business concerns from the actual ejb class. But i have been recommending not to adopt this design as we may loose some of the features provided by the EJB Container like SessionContext handling etc.
It would be great, if all of you could share your thoughts. Your suggestions would really help us to make a decision.
Actually speaking hibernate query language supports > < >= <=. I was able to solve this problem by using to_date(to_char functions in my hibernate query language