Announcement Announcement Module
No announcement yet.
General Arc Question: Use of Spring (but not EJBs) business delegates Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • General Arc Question: Use of Spring (but not EJBs) business delegates

    Before I ask my "general" question, I wanted to present some quotes to my high-level general understanding of the business delegate pattern:

    "You want to hide clients from the complexity of remote communication with business service components."

    "You want to access the business-tier components from your presentation-tier components and clients, such as devices, web services, and rich clients."

    Lets say you have large J2EE web application. When I mean large, I mean that the application has been developed for several years and by many different people and departments. The system wasn't designed well for growth. Right now, lets say the application is configured with one web application.

    It would have been great if the application were more modular. But it isn't. One piece of code or library can bring down the entire system. Testing and other means are used to prevent this, but ideally this is just one monolithic web application.

    Here is my question; how do you normally avoid this type of design with J2EE apps, where the application grows and grows and one separate application can bring down everything.

    I am not familiar EJBs and don't plan on using them for anything too serious. But, the concept of the Business Delegate and Service Locator Pattern seems like a good fit.

    Lets say you have a shopping cart screen (same web app) and a set of screens for managing a user account (same web app). In your web-tier (some kind of MVC action method), it seems you could have a Locator that will get the business specific interface, invoke those interfaces per module and if something goes wrong with that module then it doesn't kill other code. Lets say the shopping cart module fails (for whatever reason), the user account screen still works.

    Is it possible to use "Spring oriented" business delegate approach but not use the J2EE EJBs?

    Does this solution even seem to fit the problem?