• 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 Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Is this a good way of using EJBs?

 
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hi all,
My project is completely dependent on asynchronous messaging..so MDBs are natural choice.
but project also involves webservices invocation , persistence (entity are strict no-no) and some other business logic.
so i meant was
client=>MDB=>session bean>>persistence,service invocations etc..
so in this case MDB merely picks up the message when it arrives and then call a local session bean with the data from the message.the session bean carries out the business logic.
the alternative is to have the business logic in the onMessage method of MDB.
I am thinking in terms of performance,transations and scalability
i hope i have cleared out my requirements.
experts what's your call..
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
If you have the business logic in the session bean it becomes more resuable as it can be used in situations when MDB is not involved.
 
Message for you sir! I think it is a tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic