Problem is few components use DB queries...so if page which is not using that component calls it, then there is unnecessary overload !
Howard Lewis Ship wrote: > > a) Why do you care? That's more than just flippant, it indicates that if > you > are concerned about when or in what order your components are > instantiated, > you are likely setting yourself up for deployment failure. A code smell > for > this is a static variable in a component. Remember that pages and > compnents > are instantiated as needed, will be reused across different clients and > discarded when Tapestry feels they are no longer needed. > b) Tapestry instantiates pages to verify that the target of a PageLink > component is valid. You are probably seeing component instantiations > related > to that. > > On Sat, Jul 4, 2009 at 7:20 AM, Captain Cid > <captain_...@indiatimes.com>wrote: > >> >> Hi, >> >> I have 2 packages >> >> tapestry.pages.view >> and tapestry.components >> >> When i am opening some page say /view/A, i find components getting >> invoked >> which are not mentioned in A.tml or A.java . How can i stop it from >> invoking >> non used components ? >> -- >> View this message in context: >> http://www.nabble.com/Component-initialization-tp24335036p24335036.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 >> >> > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > Director of Open Source Technology at Formos > > -- View this message in context: http://www.nabble.com/Component-initialization-tp24335036p24337139.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