Hey Marius,
Thanks for clearing things up :) I'll see if I'm able to get something
working.
Cheers,
Mads Hartmann Jensen
--
You received this message because you are subscribed to the Google Groups
Lift group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from
Folks,
A quick update on Lift 2.0 build on Scala 2.8.
Scala 2.8 port of Lift is available on the branch 280_port_refresh. This
is a 'refresh'ed version of 280_port which is fully aligned and sync'ed
with the master.
To ensure minimal delta between the master and 280_port_refresh, the
On 01/23/2010 11:32 AM, Marius wrote:
Well that just the standard session behavior but if you want
JSESSIONID in the URL yu should probbaly turn off cookies in Jetty (or
whatever container you have). Thus the URL's from the page would
be something like:
On Jan 24, 10:47 am, Indrajit Raychaudhuri indraj...@gmail.com
wrote:
To ensure minimal delta between the master and 280_port_refresh, the
codebase in master has been adjusted considerably to improve Scala 2.8
compatibility. Thus, the master branch continues to be on Scala 2.7.7
but is lot
On Jan 24, 9:29 pm, Nolan Darilek no...@thewordnerd.info wrote:
On 01/23/2010 11:32 AM, Marius wrote:
Well that just the standard session behavior but if you want
JSESSIONID in the URL yu should probbaly turn off cookies in Jetty (or
whatever container you have). Thus the URL's from the
I have been developing my Lift app using the Jetty plugin on Windows,
but now am deploying production on a Tomcat 6 server on Solaris. I
don't exactly have great details at this moment, but I will admit that
I am observing some behavior differences in Tomcat that I don't see
with Jetty. I do
Awesome!
Heiko
On Sunday, January 24, 2010, Indrajit Raychaudhuri indraj...@gmail.com wrote:
Folks,
A quick update on Lift 2.0 build on Scala 2.8.
Scala 2.8 port of Lift is available on the branch 280_port_refresh. This is a
'refresh'ed version of 280_port which is fully aligned and
If you're using ProtoUser you can override the relevant method so that when the
user logs out you can take some action.
-
Daniel Spiewakdjspie...@gmail.com wrote:
This seems to work very nicely. Well, it gives me lots of spurious
events, but a little bit of
Freezing randomly is usually gc related. I'd look at memory settings.
On Jan 24, 2010 3:10 PM, aw anth...@whitford.com wrote:
I have been developing my Lift app using the Jetty plugin on Windows,
but now am deploying production on a Tomcat 6 server on Solaris. I
don't exactly have great details
So I've taken the Couch integration I had previously talked about and have done
quite a bit of work on it:
- Now has a record integration:
- built with two layers -- JSONRecord which is a Record implementation that
emits/consumes lift-json AST, and CouchRecord extends that with database
David,
I tested it on OSX 10.6. Can you try with Java 6 first? You'd need to
set JAVA_HOME explicitly in OSX 10.5.
Additionally, Is your local folder location clean? The directory
structure in 280_port and 280_port_refresh are quite different. You
might want to do mvn clean in one branch
Never mind, seems to be solved now.
In fact, quite often Maven users fall over this on OSX. I used to keep
JAVA_HOME set in ~/.profile in 10.5 for this reason.
Cheers, Indrajit
On Jan 25, 10:20 am, Indrajit Raychaudhuri indraj...@gmail.com
wrote:
David,
I tested it on OSX 10.6. Can you try
If you are using Comet with Tomcat that Lift doesn't have Tomcat async
stuff implemented and commet is implemented using locks. Thus you'd
end up having threads in wait state on reasonable high load
potentially leading to freeze.
I've recently added support for jetty 7 by adding an abstraction
On Fri, Jan 22, 2010 at 5:25 PM, David Pollak
feeder.of.the.be...@gmail.com wrote:
Folks,
Please join me in welcoming Jeppe as a Lift Committer. He's been helping
people on the Lift list and contributing his thoughts to the Lift community
for a while... now it's time for him to contribute
14 matches
Mail list logo