Should I model this object as Entity Bean ?
Hi all !
I'm modelling an application for selling tickets on-line.
Tickets are booked on-line then the user navigates to the payment page and pays with credit card.
The business analyst decided to allow a 30 minutes reservation time for people who booked the ticket to pay with credit card.
If time elapses the seat "lock" is released.
I think there should be an EJB responsible to keep up with Seat reservations.
My dilemma is : should I model it as Session Bean or Entity Bean ?
I initially modelled it as Session Bean with plain (Insert/Update) of the Seats Table when the ticket is booked / paid / time elapsed
On the other hand I think, if there's multi-user access of the PK (SeatId),
an Entity Bean should be used.
What do you say to it ? Session Bean or Entity Bean ?
Thanks in advance
Francesco
