> (1) Put a conditional check in velocity template while Most of the developers I work with do this because as you said, it's easier. At least at first.
#if($StockManager.isAvailable($book.number)) Problems surface when the rule changes. Example -- show the book if it isAvailable() or if the current user is an InventoryManager who might need to update the inventory number. #if($StockManager.isAvailable($book.number) || $UserManager.isInventoryManager()) And then, the rule always changes again... you get the picture. :-) > (2) Another approach is to check this in VARIOUS actions > while creating the > list itself if the book should be added to the list at all. I think that is a solid step in the right direction. Personally, I try to move the biz decisions further into the business layer. booklist = myStockManager.getAvailableBooksforUser(thisUser); The less the template and Struts action knows about my [oft changing] Business rules, the better IMHO. :-) Cheers, Timo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
