Glenn, I read with interest your mail below - to clarify, you've not been "hammered" by anyone... The lift comunity is a welcoming one and at no point would any member of the commit team shout down someone else - that's just not the way we roll.
You expressed a viewpoint, and 4 seperate members of the team replied asking for various things to properly answer your mostly vauge question / comments. You chose to not answer these questions in a sucinct way which is why I suspect you feel "hammered" because people are just becoming a little frustrated with this thread... As a general rule, were really pleased when people come to the comunity and say something like "XYZ feature is whack, it should do ABC" - Lift simply wouldn't be what it is today if that didn't happen. However, coming on list and saying something like "lift is difficult to integrate" and provide no clarity or justification is, well, somewhat difficult and not overly helpfull - you won't get the answers you seek and everyone else just gets more email landing in there inbox :-) If you have a genuine hurdle, post a message, with relevant details, and you'll get a prompt and informative reply from either a lift team member or one of the great folks from the comunity at large. My suggestion to you: spend some time *really* getting to know lift, then perhaps re-visit this thread at a later date if you still feel the need to. Cheers, Tim Sent from my iPhone On 14 May 2009, at 22:08, glenn <[email protected]> wrote: > > I've been hammered on this matter and I accept the results and learned > some things in the process. In the end, what we end up with > is a Java EE web application, with all the good and all the baggage > that entails, and I rather like lift's templating strategy > and out-of-the-box persistence capability . I'm working on integrating > with an ATOM server and if I run into > some difficulties, I'll post them. Over and out. > > On May 14, 1:45 pm, "marius d." <[email protected]> wrote: >> If you think that Lift does not provide enough support for what you >> are trying to do please be more specific otherwise you are risking to >> not be taken seriously and that would be a shame ... >> >> On May 14, 8:39 am, glenn <[email protected]> wrote: >> >>> I appreciate all the comments on lift and interoperability. What I'm >>> hearing >>> is that if an integration can be done in a plain old Java EE >>> application, it can be done >>> in lift. I never doubted that. It's just that I was hoping for a >>> little transparency when it >>> comes to resource management. >> >>> If I want to grab a resource outside the lift application context, >>> do >>> I write plain html, Java EE code, lift code, >>> or a hybrid? I can use an action attribute on an html form to >>> submit a >>> request to any URL, >>> but I can't do that in a lift form template. >> >> What you mean you can't do that? ... If you want to subnit forms to >> outside of the Lift app you can do that. You can even tell Lift what >> request should not be processed by Lift but passed along to the >> filter >> chain. >> >> >> >>> Lift has api's to construct and process JSON and ATOM formats and >>> even >>> has REST methods to process them, >>> but only if you plan on talking to yourself. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
