The fix is pushed up.  Please wait for Build 345 to complete and then do an
mvn -U clean install:

http://scala-tools.org/hudson/job/lift/345/

On Tue, Feb 17, 2009 at 2:17 PM, David Pollak <[email protected]
> wrote:

> Alan,
>
> The problem was not a result of yesterday's change, but I will fix it.
>
> Also, it's very important to keep all Lift-related communications on-list.
> If I'm swamped for a day or two, there are other people on the list who can
> help you.
>
> Thanks,
>
> David
>
>
> On Tue, Feb 17, 2009 at 2:12 PM, Alan Mortensen 
> <[email protected]>wrote:
>
>> Here's the stack trace:
>> java.lang.NullPointerException
>>        at net.liftweb.http.Req$$anonfun$3.apply(Req.scala:77)
>>        at net.liftweb.http.Req$$anonfun$3.apply(Req.scala:75)
>>        at net.liftweb.http.Req.x$13(Req.scala:255)
>>        at net.liftweb.http.Req.paramNames(Req.scala:252)
>>        at net.liftweb.http.Req.toString(Req.scala:228)
>>        at java.lang.String.valueOf(String.java:2615)
>>        at scala.StringBuilder.append(StringBuilder.scala:234)
>>        at
>> com.facetinnovations.diagnoser.contenttools.contentservice.ClusterHandler$$anonfun$dispatcher$1.apply(ClusterHandler.scala:28)
>>        at
>> com.facetinnovations.diagnoser.contenttools.contentservice.ClusterHandler$$anonfun$dispatcher$1.apply(ClusterHandler.scala:24)
>>        at
>> net.liftweb.util.NamedPF$$anonfun$applyBox$1.apply(NamedPartialFunction.scala:91)
>>        at
>> net.liftweb.util.NamedPF$$anonfun$applyBox$1.apply(NamedPartialFunction.scala:91)
>>        at net.liftweb.util.Full.map(Box.scala:330)
>>        at
>> net.liftweb.util.NamedPF$.applyBox(NamedPartialFunction.scala:91)
>>        at net.liftweb.http.LiftServlet.doService(LiftServlet.scala:161)
>>        at
>> net.liftweb.http.LiftServlet$$anonfun$doIt$1$1.apply(LiftServlet.scala:103)
>>        at
>> net.liftweb.http.LiftServlet$$anonfun$doIt$1$1.apply(LiftServlet.scala:103)
>>        at
>> net.liftweb.util.TimeHelpers$class.calcTime(TimeHelpers.scala:241)
>>        at net.liftweb.util.Helpers$.calcTime(Helpers.scala:29)
>>        at
>> net.liftweb.util.TimeHelpers$class.logTime(TimeHelpers.scala:250)
>>        at net.liftweb.util.Helpers$.logTime(Helpers.scala:29)
>>        at net.liftweb.http.LiftServlet.doIt$1(LiftServlet.scala:102)
>>        at net.liftweb.http.LiftServlet.service(LiftServlet.scala:111)
>>        at
>> net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1$$anonfun$apply$23.apply(LiftServlet.scala:521)
>>        at
>> net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1$$anonfun$apply$23.apply(LiftServlet.scala:521)
>>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>>        at net.liftweb.http.URLRewriter$.doWith(Req.scala:385)
>>        at
>> net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1.apply(LiftServlet.scala:520)
>>        at
>> net.liftweb.http.LiftFilterTrait$$anonfun$doFilter$1.apply(LiftServlet.scala:514)
>>        at
>> net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5$$anonfun$apply$6.apply(Vars.scala:197)
>>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>>        at
>> net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4$$anonfun$apply$5.apply(Vars.scala:196)
>>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>>        at
>> net.liftweb.http.RequestVarHandler$$anonfun$apply$3$$anonfun$apply$4.apply(Vars.scala:195)
>>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>>        at
>> net.liftweb.http.RequestVarHandler$$anonfun$apply$3.apply(Vars.scala:194)
>>        at net.liftweb.util.ThreadGlobal.doWith(ThreadGlobal.scala:65)
>>        at net.liftweb.http.RequestVarHandler$.apply(Vars.scala:193)
>>        at
>> net.liftweb.http.LiftFilterTrait$class.doFilter(LiftServlet.scala:513)
>>        at net.liftweb.http.LiftFilter.doFilter(LiftServlet.scala:532)
>>        at
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1115)
>>        at
>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:361)
>>        at
>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
>>        at
>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
>>        at
>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:766)
>>        at
>> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:417)
>>        at
>> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:230)
>>        at
>> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
>>        at
>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
>>        at org.mortbay.jetty.Server.handle(Server.java:324)
>>        at
>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
>>        at
>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:880)
>>        at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:746)
>>        at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:212)
>>        at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
>>        at
>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:409)
>>        at
>> org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
>>
>> Alan
>>
>> On Tue, Feb 17, 2009 at 1:54 PM, David Pollak
>> <[email protected]> wrote:
>> > Can you provide a stack trace?
>> >
>> > On Tue, Feb 17, 2009 at 1:52 PM, Alan M <[email protected]>
>> wrote:
>> >>
>> >> I think the update you made may have a flaw.  It seems it causes a
>> >> nullpointer exception when trying to toString a Req object.  This
>> >> worked before just fine.. and the object itself is not null.. Actually
>> >> I'm not toStringing it directly.. I'm just doing println(myReq), which
>> >> should print null if it was null.
>> >>
>> >> Alan
>> >>
>> >> On Feb 16, 4:36 pm, David Pollak <[email protected]>
>> >> wrote:
>> >> > On Mon, Feb 16, 2009 at 4:34 PM, Alan M <[email protected]>
>> >> > wrote:
>> >> >
>> >> > > OK just to wrap up for me, because I didn't really follow all the
>> >> > > implications of the change being made..  If I send a Put to a lift
>> web
>> >> > > service I should not be able to see the "file" content in the body
>> of
>> >> > > the Request?  (now as in when the update is live/updated on my
>> Maven)
>> >> >
>> >> > yes.  And the code is live, so please do an mvn -U clean install and
>> you
>> >> > should see the body of a PUT as long as the Content-Type is not form
>> or
>> >> > multi-part.
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > > Alan
>> >> >
>> >> > > On Feb 16, 3:47 pm, David Pollak <[email protected]>
>> >> > > wrote:
>> >> > > > On Mon, Feb 16, 2009 at 3:44 PM, Tim Perrett <
>> [email protected]>
>> >> > > wrote:
>> >> >
>> >> > > > > It appears that DPP is solving your issue now :-)
>> >> >
>> >> > > > > However, for the record, I do exactly what you describe in
>> terms
>> >> > > > > of
>> >> > > > > PUT / POST - this is a fairly normal ROA (but with objective-c
>> >> > > > > clients, not javascript). FYI... if you have xml messages, you
>> can
>> >> > > > > access the xml automagically in your dispatching:
>> >> >
>> >> > > > > req.xml_? // => boolean to check if its an xml body
>> >> > > > > req.xml // => the actual xml passed (do whatever parsing)
>> >> >
>> >> > > > > Not sure if im adding any value to this conversation - so
>> please
>> >> > > > > say
>> >> > > > > if im just confusing you! REST services in lift is something I
>> >> > > > > care
>> >> > > > > about a lot and ensuring its correct is of great importance to
>> me
>> >> > > > > :-)
>> >> >
>> >> > > > Tim,
>> >> >
>> >> > > > The Lift bug was that it was not respecting the Content-Type
>> except
>> >> > > > in a
>> >> > > few
>> >> > > > cases.  The change is better all around and I believe will
>> support
>> >> > > > any
>> >> > > mime
>> >> > > > type with more flexibility.  The current "special case" mime
>> types
>> >> > > > are
>> >> > > XML,
>> >> > > > multi-part mime, and forms.  All other mime types will just pass
>> the
>> >> > > request
>> >> > > > body on the Req instance.
>> >> >
>> >> > > > This should make doing web services better in Lift.
>> >> >
>> >> > > > Thanks,
>> >> >
>> >> > > > David
>> >> >
>> >> > > > > Cheers, Tim
>> >> >
>> >> > > > --
>> >> > > > Lift, the simply functional web frameworkhttp://liftweb.net
>> >> > > > Beginning Scalahttp://www.apress.com/book/view/1430219890
>> >> > > > Follow me:http://twitter.com/dpp
>> >> > > > Git some:http://github.com/dpp
>> >> >
>> >> > --
>> >> > Lift, the simply functional web frameworkhttp://liftweb.net
>> >> > Beginning Scalahttp://www.apress.com/book/view/1430219890
>> >> > Follow me:http://twitter.com/dpp
>> >> > Git some:http://github.com/dpp
>> >
>> >
>> > --
>> > Lift, the simply functional web framework http://liftweb.net
>> > Beginning Scala http://www.apress.com/book/view/1430219890
>> > Follow me: http://twitter.com/dpp
>> > Git some: http://github.com/dpp
>> >
>>
>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Beginning Scala http://www.apress.com/book/view/1430219890
> Follow me: http://twitter.com/dpp
> Git some: http://github.com/dpp
>



-- 
Lift, the simply functional web framework http://liftweb.net
Beginning Scala http://www.apress.com/book/view/1430219890
Follow me: http://twitter.com/dpp
Git some: http://github.com/dpp

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

Reply via email to