Sorry if this question is a bit basic, but I'm having a hard time wrapping my head around a few concepts with IOC and how it works in general and with Tap specifically.
Basically, I get held up with simple stuff like creating a new Entity instance for an object (like a Hotel Reservation) that belongs to a logged in user. The user is logged in, we are going to the Make a reservation page, now what's the best way to do this? There has to be some way to supply the logged in user to the Hotel Booking at some part in the process but I don't see specific instructions on how this happens. Can anyone point me to a good resource/write-up? Of course the Hotel Booking Application addresses this specific problem but it seems to wrap across 5 or 6 different POJOs, Views, Page Classes, etc. and is not very straightforward to me. It looks like it uses a DAO to get the User in a /View/ class, which then turns control over to the Book POJO which... I don't know, I get a little lost at this point. Is the Authenticator model implemented in com.tap5.hotelbooking.services the best way to go? -- View this message in context: http://tapestry.1045711.n5.nabble.com/Understanding-Entities-with-Entities-in-the-Tapestry-Framework-tp5579217p5579217.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
