Win a copy of Svelte and Sapper in Action this week in the JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Command pattern vs Session Facade

Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I am debating using the Command pattern as my primary strategy for implementing my J2EE enterprise app business logic and would like some advice.

The general idea is to have only a few types of abstract commands (such as a NonTransactionalCommand, a TransactionalCommand -- I might have a slightly finer granularity than this, I don't know) and implement each use case as a command instance. For example, I might have a command called GetProductListCommand which is a NonTransactionalCommand and returns the list of products available (i.e., has a getProducts() method) when execute()'d.

The result of my design will be a very small set of stateless session beans with an execute() interface. No entity beans (will use Hibernate) and may very well eventually implement a Message bean interface with a similar executeAsynchronously() type method, if eventually necessary.

I guess the popular alternative (or, more correctly, the norm) is to implement session facades for this.

However, I am attracted to the Command pattern because of its simplicity, it's rapid application development angle, its disconnected-ness from EJB (e.g., a modification to a command does not mean touching any EJB at all, just the command class), and the ability for implementing cross-cutting features (such as transactions or security, although I also plan to use an AOP solution at the POJO level). At the same time, it works as a delegate of an EJB, so it's accessible for all kinds of network clients.

I am also familiar with it's drawbacks (e.g., maintainability for large numbers of commands, per the literature, such as the Marinescu 2002 EJB Patterns book).

So, very few types of stateless session beans (though there may be many instances) -- mainly there for remote client acceessibility and the ability to leverage application-level transactions if needed.

Nevertheless, I have never tried the command pattern approach and was curious if others had feedback or case studies.

Best regards --
I promise I will be the best, most loyal friend ever! All for this tiny ad:
Thread Boost feature
    Bookmark Topic Watch Topic
  • New Topic