I think my simple solution does not work... and the implementation of
MappedPassword is not really easy to understand. I thought such
classes
would be nice for datatypes as Currency, Timespan etc... that appear
everwhere
in the application but where own tables are not useful.
The solution of
On Sat, Oct 17, 2009 at 11:07 AM, johncch john...@gmail.com wrote:
I manage to import lift and lift-mapper projects fine, but earlier
today when I tried importing in lift-hello lift I'm getting editor
shutdowns and what nots. Let's look at a few.
From the stacktrace my hunch is that you're
I'm not supporting the mvn eclipse:eclipse plugin route right now. If
anyone desires to support that, please contribute patches ;)
On Sat, Oct 17, 2009 at 8:58 AM, Miles Sabin mi...@milessabin.com wrote:
On Sat, Oct 17, 2009 at 11:07 AM, johncch john...@gmail.com wrote:
I manage to import
On Sat, Oct 17, 2009 at 2:31 PM, Josh Suereth joshua.suer...@gmail.com wrote:
I'm not supporting the mvn eclipse:eclipse plugin route right now. If
anyone desires to support that, please contribute patches ;)
So, for the archives, could you say what the currently recommended
Maven+Eclipse
It's gotten to the point where I can only support the configuration we're
using at work (as it's critical to our success).
At one point I thought I had written how on this wiki:
http://lampsvn.epfl.ch/trac/scala/wiki/ScalaEclipseMaven, but it seems like
I've missed that. Also, it seems some of
Perhaps supporting optional alias registration for types (case
classes) could be a way to reduce domain coupling. It could be used to
provide a level of abstraction. Granted it's more work to initialize
so there are drawbacks.
On Oct 17, 4:40 am, Marius marius.dan...@gmail.com wrote:
Hmmm ... I
I've been thinking this feature today a bit too. Marius raises an
important point. Adding type information and more complex
serialization scheme will introduce couplings, making it for instance
more difficult to deserialize JSON using a different language or
toolkit. On a positive side, we might
Sorry for cross-posting here, I think I have a valid reason... :)
I've spotted that the BASE crowd have a scala wave going, has anyone
yet thought to do the same for scala globally?
Same question goes to lift users.
--~--~-~--~~~---~--~~
You received this
On Sat, Oct 17, 2009 at 2:42 AM, hyperion hyperion1...@googlemail.comwrote:
I think my simple solution does not work... and the implementation of
MappedPassword is not really easy to understand. I thought such
classes
would be nice for datatypes as Currency, Timespan etc... that appear
On Sat, Oct 17, 2009 at 7:54 AM, Joni Freeman freeman.j...@gmail.comwrote:
I've been thinking this feature today a bit too. Marius raises an
important point. Adding type information and more complex
serialization scheme will introduce couplings, making it for instance
more difficult to
That was not my solution but harryh's, I believe.
Of course the downside of it is that there's a limit of 1 timespan per record.
-
hyperionhyperion1...@googlemail.com wrote:
I think my simple solution does not work... and the implementation of
MappedPassword
Currently lift-openid is using openid4java 0.9.3, which is a little
old and is difficult to find a maven repository to download.
I think changing lift-openid's pom with a newer one, like
openid4java-0.9.5 will be better. (works fine on my machine)
12 matches
Mail list logo
