Sounds good. Don't hesitate to ask questions if you run into issues or if
there's something not clear in the API.
Derek
On Tue, May 19, 2009 at 3:08 AM, rintcius rintc...@gmail.com wrote:
I have decided to develop a little example project that looks at using
scala from the perspective of
Glenn,
It's easy for emails communications to go south. i'd be more than happy to
help you out, but being a pretty slow guy, i need a specific code context
before i can really grok what it is you want to do. If you're worried about
IP or disclosure, can you cook up a simplified version with the
Yeah, that's the ticket. You've got a new technology or framework you
want to promulgate,
insult the one's who don't get it out of the box. A bit mean-spirited,
don't you think.
Frankly, lift raises more questions then it answers. That's not a
complaint..
I don't get it. I don't get that I have
Glenn, most of the people on this list have come to Lift knowing pretty much
nothing about it. Most of the people on this list have also read the APIs,
source, and asked a ton of questions to learn about Lift and how it works.
Very few other people on this list that I can recall have made
Interesting discussion! I think I see a bit where Glenn is coming
from. To me it's about *ease* of interoperability.
For enterprise architectures the most important question is: to what
extent is Lift helping me to build a **composable** software system.
A composable software system will offer
On May 17, 4:33 am, rintcius rintc...@gmail.com wrote:
Interesting discussion! I think I see a bit where Glenn is coming
from. To me it's about *ease* of interoperability.
For enterprise architectures the most important question is: to what
extent is Lift helping me to build a
Hello guys,
if you could scribble together a scenario, then I might be able to help you
out.
Cheers,
On Sun, May 17, 2009 at 10:53 PM, johnnie jsm2p...@googlemail.com wrote:
On May 17, 4:33 am, rintcius rintc...@gmail.com wrote:
Interesting discussion! I think I see a bit where Glenn is
On Sun, May 17, 2009 at 2:33 AM, rintcius rintc...@gmail.com wrote:
Interesting discussion! I think I see a bit where Glenn is coming
from.
I'm all for interoperability... I like baseball and apple pie, too. If
there is a problem with Lift interoperating with another system or another
piece
Tim,
i'm really impressed -- you typed all that on you iPhone?
Best wishes,
--greg
On Thu, May 14, 2009 at 4:48 PM, Timothy Perrett timo...@getintheloop.euwrote:
Glenn,
I read with interest your mail below - to clarify, you've not been
hammered by anyone... The lift comunity is a
Hey Greg, lol, indeed I did write that all on my iphone (hence some
crappy spelling mistakes!)
Cheers, Tim
On May 15, 11:53 am, Meredith Gregory lgreg.mered...@gmail.com
wrote:
Tim,
i'm really impressed -- you typed all that on you iPhone?
Best wishes,
--greg
On Thu, May 14, 2009 at
On May 11, 9:59 pm, Meredith Gregory lgreg.mered...@gmail.com wrote:
Glen,
i've done some really hare-brained integrations -- like chaining the Lift
filter with the Jersey filter -- and a bunch of other stuff. Between Lift's
architecture and Scala's brilliant interop with Java, it's
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
Glenn,
i'm not sure i've understood your concern. Are you saying that
- web requests - lift are easy, but
- lift - other services (web or otherwise) are hard?
The latter direction is remarkably easy. Lift rests on top of Scala, Scala
seamlessly interops with Java. So, anything you can do
Glenn,
On Wed, May 13, 2009 at 10:39 PM, glenn gl...@exmbly.com 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
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
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
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
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
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
Glen,
i've done some really hare-brained integrations -- like chaining the Lift
filter with the Jersey filter -- and a bunch of other stuff. Between Lift's
architecture and Scala's brilliant interop with Java, it's definitely my
weapon of choice for integration projects.
That said, i would
20 matches
Mail list logo
