The first suggestion was reflection... I'm not pushing the idea, just throwing in an alternative. But the xml route doesn't have to be xml--it could be a plain text file like /META-INF/.liftboot etc. Or you could search all jars for net.liftweb.BootXX or net.liftweb.XX that implements a trait OnBoot... The point is, there's no shortage of ways (if there's a will :) ) but they all have a certain cost of course. Dynamic loading _means_ searching for Something. That takes time, and it puts some requirement on the library author--but it takes the requirement off the user.
------------------------------------- Timothy Perrett<[email protected]> wrote: Hey Naftoli, Lift has a general aversion to xml configs... Is there another route? Cheers, Tim On 28/07/2009 20:47, "Naftoli Gugenheim" <[email protected]> wrote: > > What I was suggesting is that instead of having to write Lib.init in Boot, > Lift should look in Lib.jar for say /boot.xml which would tell Lift to execute > Lib.init for you on startup. I think that would accomplish what you want, at > the cost of lift searching through the jars. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
