Could agree more with Alex - I too have done some pretty sophisticated integrations with 3rd party systems and at every stage I found the life-cycle hooks into lift very rich and completely empowering.
Cheers, Tim On May 11, 11:31 pm, Alex Boisvert <boisv...@intalio.com> wrote: > Hi Glenn, > > I don't understand where you're coming from either... I've integrated Lift > with a different persistence layer (home-grown), another authentication > system (Tempo RBAC), integrated it with existing Java libraries and Spring > MVC components without trouble. So far, I haven't run into a situation > where Lift got in the way of integration. The fact that Lift uses all the > standard servlet APIs made it easy to simply add it to an existing app and > even reuse session state / cookies from existing apps. > > I can see how Lift can be different from what you're used to, but I don't > see how Lift gets in the way of integrating with legacy apps. > > My 2 cents... > > alex > > > > On Mon, May 11, 2009 at 1:06 PM, glenn <gl...@exmbly.com> wrote: > > > Just some observations from a struggling lift user... > > > Yes, I see it's utility in delivering dynamic html to the browser. But > > in today's world of rapidly evolving technologies for mashups and flex- > > like richness and gadgetization, interoperability is the key to > > adoption in the enterprise. It's not enough to say you can selectively > > rewrite your legacy apps in lift. Lift, out of the box, is still > > another technology for building monolithing web apps (war files). Not > > the best stategy. > > > I find the keepers of the code, in response to numerous postings on > > this site, suffer from NIH anxiety and easily dismiss interoperability > > with other frameworks, either because they believe they have a > > superior implementation, so why use someone else's, or, if you really > > feel you need it, roll your own. > > > My response to that is, it just doesn't work that way. The best > > technologies are not just agnostic on the issue of interoperability, > > they embrace pluggability, and let the developer community choose the > > winners and losers. > > > Lift suffers from not even having an out-of the-box declarative > > configuration capability. And, frankly no, I don't have the time or > > resources to write my own. Please, give me something other than just > > an <a> tag to work with. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
