I am currently developing a small-ish web application using tapestry &
trails, and was hoping someone might give an opinion on a design issue:
I have a userAccount object, which has collections of objects associated
with it in hibernate. What this means is that I need to have the
hibernate id of the userAccount object for the user currently logged in
(because it would be inappropriate to make them select it from a list of
all accounts on the system)... What is the best way of achieving this?
Because the userAccount Object would potentially get quite large, would
a good solution be as follows:
1. Create a small CrucialInfo object and store the id of the account
(along with anything else i havent thought of yet) in this
2. Store that object using hivemind as a session state object
3. Inject the CrucialInfo object into the appropriate pages
4. Read the accountId from the injected CrucialInfo object just before
child objects are persisted to the database
Trails has the concept of of a defaultEdit page... assuming the above
solution is good, is reflection a good way to store that accountId value
into a (always the same) field on the objects, essentially by extending
the org.trails.EditPage?
Thanks
Gareth Deli
[EMAIL PROTECTED]
___________________________________________________________
24 FIFA World Cup tickets to be won with Yahoo! Mail http://uk.mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
