EJBs and MDBs in a Service Provider.I need some URGENT help plz
Posted on 2004-04-26
Hello all ..
im actually about to design a distributed service provider across a LAN..users register at a service provider server and then receive messages through their pc., namely an alert service and chat system. I would be using JMS with the publish subscribe model in the J2EE environment..i have downloaded the SunOne application server bundle which includes Sun Message Queue as JMS provider.
The basic technology decisions for the implementation of this application are as follows:
· A Java-based client side application for users to interact with. The SWING (JFC) toolkit will be used.
· A J2EE-compliant application server to handle the middleware chores. (SUN ONE Application Server)
· A JMS-complaint messaging product to tie all the subsystems together. (SUN ONE Message Queue, which is bundled within SUN ONE application server.)
· A database server
Ive read about EJBs(Session beans, entity beans) and the new Message Driven Bean. My design problem is that I don’t know how many beans are needed to implement the system. Users will have to login into the system, and their credentials shall be checked to those in the remote database located on the server. Upon successful login, if there are any messages pending for them, they could be sent to their pc (alert service).
Also, I’d like to know what is the functionality of each bean. Can you plz provide some light on this design issue?
Thanks a lot..
Hoping a reply from you soon,