This has not so much to do with IOC as more with settting up your database and business logic and tie them together.
If you have a logged in user, i assume you'll have some database record of this user ? Then the user will have a unique key (most likely an id). Now when creating a hotel booking you just create a new hotel booking entry in the database using a HotelEntity instance and link this to the user via it's primary key. Save the hotel booking and the next time the user logs in , you can retrieve his/her bookings by querying all bookings where the field userid is that of the logged in user. And display these bookings in a grid or something like that. ?! I hope this answers some of your questions. Antal -- View this message in context: http://tapestry.1045711.n5.nabble.com/Understanding-Entities-with-Entities-in-the-Tapestry-Framework-tp5579217p5579340.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
