We are trying to design a web application on Websphere. The design decisions made are: Presentation layer is on STRUTS framework. Data layer is based on a custom framework that. We are in the process of designing business layer for the application. It is also decided that we will not be using EJBs and will stick to Plain old java objects (POJOs).
What design patterns can be used in the business layer? Almost all the J2EE patterns are discussed with EJB in mind. How applicable are the J2EE design patterns in this kind of approach? Please help………..
I've noticed a strong correlation between people talking about 'patterns' and people using EJB. Since Marinescu's EJB Design Patterns and that Wrox book - was it 'Core J2EE Patterns?', I think everyone thinks EJB has a monopoly on the use of patterns. Actually there is point of view that EJB is itself an anti-pattern! Only kidding. A pattern is no more than a decent basis for a design. What were you considering EJBs for? Database access? Well there are plenty of non-EJB database access frameworks around. JDO, Hibernate. Actually I think you can pick up a free copy of EJB Patterns as a pdf from the serverside.com, and in it they have a chapter on alternatives for EJB. HTH, Adam
I have seen things you people would not believe, attack ships on fire off the shoulder of Orion, c-beams sparkling in the dark near the Tennhauser Gate. All these moments will be lost in time, like tears in the rain.
How can we use patterns like business delegate Factory Transfer object in business layer using POJOs? Is it always necessary that Transfer objects be used between business and presentation layer (STRUTS) or can business objects be returned as it is??