[Lift] Re: ANNOUNCE: New functionality for Mapper logging with breaking changes

[Vassil]

Hello,

Shouldn't S.logQuery and S.queryLog be updated as well or deprecated
if they're not going to be used the way they were as parameters to
DB.addLogFun?

Thanks,
Vassil
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] Re: lift-openid broken

[Vassil]

> Done.

Great, propagated to maven repo now. Thanks.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] lift-openid broken

[Vassil]

Hello guys,

It seems the HTTP refactoring around 10 days ago broke OpenId. Here's
a small patch that made it work for me:

--- dpp-liftweb-e845b3c129baf16bc35b46df9ee5b5049d4aee3a/lift-openid/
src/main/scala/net/liftweb/openid/OpenId.scala 2009-08-16
17:36:58.0 +0300
+++ dpp-liftweb-fixed/lift-openid/src/main/scala/net/liftweb/openid/
OpenId.scala2009-08-17 01:43:46.0 +0300
@@ -267,7 +267,7 @@

 // retrieve the previously stored discovery information
 val discovered = httpReq.session.attribute("openid-disc") match {
-  case Full(d: DiscoveryInformation)=> d
+  case d: DiscoveryInformation=> d
   case _ => throw ResponseShortcutException.redirect("/")
 }

@@ -275,7 +275,7 @@
 var receivingURL = httpReq.url
 val queryString = httpReq.queryString openOr ""
 if (queryString != null && queryString.length() > 0) {
-  receivingURL += "?" + httpReq.queryString;
+  receivingURL += "?" + queryString;
 }

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---

[Lift] JSON handler doesn't respond

[Vassil Dichev]

Hello folks,

I've gathered some information on the recent problems where ESME was hanging.
The problem seems to be that the json handler, generated with
S.buildJsonFunc, sometimes stops working after the browser has been
open for awhile. Not all user sessions stop working though (I'm
currently trying with 3 open sessions).

I've also tried calling the generated JavaScript function manually
from each of the browsers and it confirms the fact that for some
sessions the handler is not invoked. I execute the function e.g. in
the url bar like this:

   javascript:F6669067195625JG({'command': 'post', 'params':{'msg':
document.getElementById('textdude').value, 'tags':
document.getElementById('tagdude').value, 'access_pool':
document.getElementById('access_pool').value, 'reply-to':
currentConvNumber}});

As a result, in the sessions where things don't work the pattern
matching on JsonCmd is not reached at all, whereas "case JsonCmd"
matches fine where it works.

Any ideas on how to debug this? Has anyone experienced the same problem?

Greetings,
Vassil

P.S. We are running Lift version 1.1-SNAPSHOT. I experienced the
problem under OpenJDK 6, but it occurs with Sun's JDK 6 too.

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Lift" group.
To post to this group, send email to liftweb@googlegroups.com
To unsubscribe from this group, send email to 
liftweb+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/liftweb?hl=en
-~--~~~~--~~--~--~---