Lift Google Group

QueryParams and joins

2010-01-04T23:24:39Z

Hello, I'm having a problem and I'm sure it's an easy fix for someone
with a bit more experience
I have 3 model classes: tag, user, tweet and a join class TagUser. A
tag has a list of users.
If i want all of the users in a tag i use the following code (which
works):
def users = TagUser.findAll(By(TagUser.tag , this.id)).map

Re: [Lift] Safe handling of long params

2010-01-04T22:37:10Z

Aha!
Thanks,
Sent from my iPhone

Re: [Lift] Safe handling of long params

2010-01-04T22:18:08Z

Ah right yeah - I thought it was implicit :)

Re: [Lift] Safe handling of long params

2010-01-04T22:09:55Z

Nope, it's not a implicit extension of String or anything, it's just a
plain method def asLong(s: String): Box[Long] in BasicTypesHelpers
-Ross

Re: [Lift] Safe handling of long params

2010-01-04T22:08:45Z

Shouldnt that be:
S.param("image").flatMap(_.asL ong)
Cheers, Tim

Re: [Lift] Safe handling of long params

2010-01-04T21:45:27Z

I can answer b) -- S.param("image").flatMap(asLon g)
asLong comes from BasicTypesHelpers.
-Ross

Safe handling of long params

2010-01-04T21:42:56Z

So, in my endless retweaking of this code, getting better (and learning
more lift) on each pass, I've got a rewrite rule like this
case RewriteRequest(ParsePath("imag e" :: image :: Nil, _, _, _), _, _) =>
RewriteResponse("viewImage" :: Nil, Map("image" -> image))
which is (eventually) handled by a snippet like this:

Re: cookie vs url sessionId precedence

2010-01-04T21:24:26Z

Using jsessionid in the URL (aka url rewriting - servlets jargon) is
about turning off cookies in container. I think with Jetty you can do
this from /WEB-INF/jetty-web.xml. Something like:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE Configure PUBLIC "-//Mort Bay Consulting//DTD Configure//EN"
"[link]">

Re: [Lift] Lift based backend server subscribing via amqp

2010-01-04T21:23:38Z

oh super awesome! I had no idea!!
Cheers, Tim

Re: [Lift] Lift based backend server subscribing via amqp

2010-01-04T21:06:56Z

Nope! We're using it in production as well. :)
Kris

Re: [Lift] Minor breaking changes -- LiftRules.getResourceAsStream and LiftRules.finder

2010-01-04T21:03:01Z

Instead of:
LiftRules.getResourceAsStream( name: String): Box[InputStream]
I'd suggest:
LiftRules.doWithResource[T](na me: String)(f: InputStream => T): Box[T].
And if you need laziness, you could use one of the usual suspects: "lazy
val", unapplied function, FatLazy, etc.
alex
On Thu, Dec 31, 2009 at 3:48 PM, David Pollak <feeder.of.the.be...@gmail.com

Re: [Lift] Re: [lift] Lift based backend server subscribing via amqp

2010-01-04T20:53:58Z

It depends on your use case... you don't really describe exactly what you want to do. Perhaps start by providing more detail? If you want service teir *only* though, its quite probable that akka would be a better fix.
Cheers, Tim

Re: source of working demo of Lift+JPA on google app engine

2010-01-04T20:53:02Z

Last time I looked just JDO yes, I didn't think it was worth it as you
cannot use most of what makes Lift special (Comet, mapper), but if
you're looking for an example check out...
[link]
(a bit dated)
[link]

Re: [Lift] Re: Minor breaking changes -- LiftRules.getResourceAsStream and LiftRules.finder

2010-01-04T20:51:42Z

On Mon, Jan 4, 2010 at 9:51 AM, David Pollak
I believe that this is actually the type signature of the Thrush
combinator - it's a pretty generally useful type. I have the following
in my codebase:
implicit def any2Thrush[T](t: T): Thrush[T] = new Thrush[T](t)
class Thrush[T](t: T) {
def ->*[U](f: T => U): U = f(t)

Re: [lift] Lift based backend server subscribing via amqp

2010-01-04T20:30:05Z

Maybe Akka would be better for you? [link]
"Akka has an AMQP module which abstracts AMQP Producer and Consumer as
Actors."
Channing