I personally pass the objects as parameters. One thing we find is that we "set out" planning to use a Custom component for one page alone, but very soon there are so many uses and variants, that it's always preferable for the component to be loosely coupled with the service layer.
Which in other words would mean pass parameters. On 9/21/06, jake123 <[EMAIL PROTECTED]> wrote:
Hi, I have a question about best practice on how to design custom component. I will write custom components for our application that will be used only in our application. Is it a good idear to let the custom component access my session object and from that call my service layer to ask for some objects or is it a better design to add object as parameters to the component? // Jacob -- View this message in context: http://www.nabble.com/Custom-Components-tf2307973.html#a6416332 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Thanks, Karthik
