Re: [Lift] URL Rewriting - 'nested' ParsePath?

2010-02-06 Thread Jeppe Nejsum Madsen
Alex Black a...@alexblack.ca writes: Hi, I'd like to rewrite a url like this: /manufacturer/product e.g. LiftRules.statelessRewrite.append( { case RewriteRequest( ParsePath( manufacturerName :: productName :: Nil, _, _,_), _, _) = RewriteResponse(productView

Re: [Lift] Re: OSGi example, what to do to make it run?

2010-02-06 Thread Heiko Seeberger
Philip, 2010/2/6 philip philip14...@gmail.com Why do I want to do that? I am making a code generator which generates Scala code, I want the user to be able to try out the Scala code. So some liftweb method would generate a .scala file and another would package it into a OSGi and load the

[Lift] Error messages are not displayed - 2.0-M1

2010-02-06 Thread wibblecp
Hi all, I'm newbie with lifts and I am having a little problem. I am using Lift2.0-M1. I have a snippet that runs the rescue of a model. The method is called when the submit the form [code] def validateAndSave (): Unit = currentEntry.validate match { case Nil = currentEntry.save ;

[Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread Marius
Are you using in your html page lift:msgs/ ? Br's, Marius On Feb 6, 10:45 am, wibblecp wibbl...@gmail.com wrote: Hi all, I'm newbie with lifts and I am having a little problem. I am using Lift2.0-M1. I have a snippet that runs the rescue of a model. The method is called when the submit the

[Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread wibblecp
Hi Marius, thanks for your raply I am using it in my html page as: [code] lift:snippet type=msgs lift:error_classflash_error/lift:error_class lift:warning_classerrorExplanation/lift:warning_class lift:notice_classflash_notice/lift:notice_class

[Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread wibblecp
Using lift:msgs/ I receive the same result. S.notice works fine in the browser but S.error with a list of errors does not work. any advice? thanks, wibble. On Feb 6, 10:16 am, wibblecp wibbl...@gmail.com wrote: Hi Marius, thanks for your raply I am using it in my html page as: [code]      

[Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread wibblecp
it does not work even in the case of a single error on the form. the result is always a List(Full(entries_code) : Description must not be empty) thanks, wibble. On Feb 6, 11:00 am, wibblecp wibbl...@gmail.com wrote: Using lift:msgs/ I receive the same result. S.notice works fine in the

Re: [Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread Jeppe Nejsum Madsen
wibblecp wibbl...@gmail.com writes: it does not work even in the case of a single error on the form. the result is always a List(Full(entries_code) : Description must not be empty) Try adding showAll: lift:Msgs showAll=true But default, Msgs doesnøt show field-level errors /Jeppe -- You

Re: [Lift] Potential breakage: Choosing the default Lift logging backend

2010-02-06 Thread Jeppe Nejsum Madsen
Heiko Seeberger heiko.seeber...@googlemail.com writes: Hi, On 5 February 2010 22:11, Jeppe Nejsum Madsen je...@ingolfs.dk wrote: 2) is the cleanest solution since the choice of logging backend is made explicit. But this requires people to change their poms in order to get any logging.

[Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread wibblecp
Hi Jeppe, lift:Msgs showAll=true does not work. Always the same result. If the form does not contain errors the data are saved well and the browser display S.notice(saved) correctly. The S.error method returns a List[FieldError]. I receive a List with the format of List(Full(tablename_field) :

Re: [Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread Adam Warski
Hello, are you submitting the form with ajax? If so, see this thread: http://groups.google.com/group/liftweb/browse_thread/thread/e25d86a24a5266a2/9fdcf9f2ce022618 In short, check if doing: xs.map {i = S.error(i.msg) }; instead of: S.error(xs); works. Hi Jeppe, lift:Msgs showAll=true

[Lift] Re: Potential breakage: Choosing the default Lift logging backend

2010-02-06 Thread Timothy Perrett
Jeppe, Certainly 2 has to be the way to go. We can add stuff to the archetypes to ease this process for users. Moreover, we could add specific lift modules that carried the right dependencies and boot wire up to save the users writing boilerplate. i.e.: + lift-logging \ - lift-log4j \ -

[Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread wibblecp
hi Adam, thank you. It is exactly what I done def validateAndSave (): Unit = currentEntry.validate match { case Nil = currentEntry.save ; S.notice(currentEntry.title + SAVED!) case x = { x map { (e:FieldError) = S.error(e.msg) } } } have a nice day. wibble On Feb 6, 2:35 pm,

Re: [Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread Timothy Perrett
wow, thats some ugly code man. Why dont you try something like: def validateAndSave { currentEntry.validate match { case Nil = currentEntry.save S.notice(currentEntry.title + SAVED!) case List(fielderror) = S.error(fielderror.msg) case _ = } } I havent tested it of

[Lift] Vim Helpers for Lift

2010-02-06 Thread TylerWeir
Antonio Salazar Cardozo put together some helpers for Vim. http://www.vim.org/scripts/script.php?script_id=2962 Currently provides a few commands: * :Lmodel, Lsnippet, Lactor, Lcomet -- all take a class name and take you to the appropriate associated file * :Lview -- takes a class name and

[Lift] Re: Lift-OpenID should default to openid_identifier for post param name

2010-02-06 Thread Erkki Lindpere
Ok, I'll do that. BTW. As I'm doing a bit of research how providers support Attribute- Exchange, it seems their behaviour and supported schemas can be quite different (for example, Google ignores optional attributes). So the function might need a parameter from which the openid provider can be

[Lift] Re: Error messages are not displayed - 2.0-M1

2010-02-06 Thread Marius
What Lift version are you using? If you are using an Ajax form lift:msgs showAll=true/ did not show the messages associated with ID's ... messages coming from FieldError. This is a defect I fixed about a week ago. Please use the latest lift build. If you just want to render all messages

[Lift] HTTP Reason Phrase

2010-02-06 Thread Erkki Lindpere
It seems Lift does not support custom HTTP Reason Phrases in responses. I would like to send error messages in the Reason Phrase (along with a vaguely applicable HTTP status code) in a RESTful API I'm providing. My understanding of the HTTP spec is that the reason phrase is meant to be human

[Lift] Re: [Lift committers] We're moving our ticketing system to Assembla

2010-02-06 Thread Indrajit Raychaudhuri
Migration complete! Please DO NOT use GitHub Issue tracking facility anymore. Use http://www.assembla.com/spaces/liftweb/tickets instead. Cheers, Indrajit On 04/02/10 2:05 AM, David Pollak wrote: Folks, On today's committer call, we made the final decision to move the Lift ticketing system

Re: [Lift] **IMPORTANT** HOLD OFF CREATING TICKETS ON ASSEMBLA

2010-02-06 Thread Indrajit Raychaudhuri
Go ahead! create tickets in Assembla. Cheers, Indrajit On 05/02/10 10:49 AM, Naftoli Gugenheim wrote: Indrajit and I are working on importing tickets into Assembla. The first ticket on GitHub is #3 and there are now two on Assembla. So please don't create any Assembla tickets until further

Re: [Lift] **IMPORTANT** TOTALLY DO CREATE TICKETS ON ASSEMBLA

2010-02-06 Thread Ross Mellgren
Also, please don't use GitHub for issues any more. Care of Indrajit, here is the new URL to submit issues: http://www.assembla.com/spaces/liftweb/tickets -Ross On Feb 6, 2010, at 3:12 PM, Indrajit Raychaudhuri wrote: Go ahead! create tickets in Assembla. Cheers, Indrajit On 05/02/10

[Lift] Forcing Authentication not working

2010-02-06 Thread aw
According to: http://scala-tools.org/mvnsites-snapshots/liftweb/lift-base/lift-webkit/scaladocs/net/liftweb/http/LiftRules$object.html#httpAuthProtectedResource It says that if I have a rule that responds with Empty, it means that authentications is performed, but not an authorization check.

Re: [Lift] **IMPORTANT** TOTALLY DO CREATE TICKETS ON ASSEMBLA

2010-02-06 Thread Indrajit Raychaudhuri
Ross, Thanks for updating the subject line and clarifying even. - Indrajit On 07/02/10 1:46 AM, Ross Mellgren wrote: Also, please don't use GitHub for issues any more. Care of Indrajit, here is the new URL to submit issues: http://www.assembla.com/spaces/liftweb/tickets -Ross On Feb 6,

Re: [Lift] **IMPORTANT** TOTALLY DO CREATE TICKETS ON ASSEMBLA

2010-02-06 Thread Ross Mellgren
hah no problem, though if I had realized initially that you had cc'd liftweb on the other thread, I probably wouldn't have ;-) -Ross On Feb 6, 2010, at 3:35 PM, Indrajit Raychaudhuri wrote: Ross, Thanks for updating the subject line and clarifying even. - Indrajit On 07/02/10 1:46 AM,

Re: [Lift] **IMPORTANT** TOTALLY DO CREATE TICKETS ON ASSEMBLA

2010-02-06 Thread David Pollak
On Sat, Feb 6, 2010 at 12:16 PM, Ross Mellgren dri...@gmail.com wrote: Also, please don't use GitHub for issues any more. Care of Indrajit, here is the new URL to submit issues: http://www.assembla.com/spaces/liftweb/tickets I have disabled the GitHub issue tracker and I have changed the

Re: [Lift] **IMPORTANT** HOLD OFF CREATING TICKETS ON ASSEMBLA

2010-02-06 Thread David Pollak
On Sat, Feb 6, 2010 at 12:12 PM, Indrajit Raychaudhuri indraj...@gmail.comwrote: Go ahead! create tickets in Assembla. Excellent job and a huge round of applause to Indrajit and Naftoli for moving the tickets over the Assembla. Thanks guys! Cheers, Indrajit On 05/02/10 10:49 AM, Naftoli

[Lift] **IMPORTANT** Lift ticketing system has moved to Assembla

2010-02-06 Thread Indrajit Raychaudhuri
Folks, Following David's announcement about moving our ticketing system to Assembla [1], the migration is complete and we have now completely moved from GitHub issues to Assembla tickets. Please DO NOT use GitHub to create issues anymore (the GitHub URL would be disabled), instead use this

[Lift] Re: [Lift Announce] **IMPORTANT** Lift ticketing system has moved to Assembla

2010-02-06 Thread David Pollak
Please note that you must register with Assembla **AND** register as a watcher of the Lift project in order to create/edit tickets. We have this rule to avoid spam in the tickets. On Sat, Feb 6, 2010 at 1:17 PM, Indrajit Raychaudhuri indraj...@gmail.comwrote: Folks, Following David's

[Lift] lift-archetype-blank 1.1-M8 2.0-M1 : missing net.sf.retrotranslator:retrotranslator-runtime:jar:1.2.1

2010-02-06 Thread Luke Nezda
Hello - I am just getting started with Lift and used the Hello, World archetype lift-archetype-blank (tried 1.1-M8 2.0-M1) and both fail to build successfully from the specified public Maven repositories with: Missing: -- 1) net.sf.retrotranslator:retrotranslator-runtime:jar:1.2.1 ...

[Lift] Re: HTTP Reason Phrase

2010-02-06 Thread Erkki Lindpere
The NotFoundResponse (and others) puts the custom message into the request body. That works as well, but to be really lean (mainly for bragging rights :)) I'd like to remove any unnecessary elements from the rest api. Most of the error messages are going to be simple one- line messages (and short

Re: [Lift] lift-archetype-blank 1.1-M8 2.0-M1 : missing net.sf.retrotranslator:retrotranslator-runtime:jar:1.2.1

2010-02-06 Thread David Bernard
retrotranslator-runtime version 1.2.1 is available in central repository (the default one) since 2007. see : http://repo2.maven.org/maven2/net/sf/retrotranslator/retrotranslator-runtime/1.2.1/ May be you tried to build offline, or you define/use wrong mirror/proxy of central repository. Do you

[Lift] Re: URL Rewriting - 'nested' ParsePath?

2010-02-06 Thread philip
Hi Alex, I am making a CMS, so I had to get database content for any page up to 4 levels under the URL http://site/page/leve1/level2/etc ... Here is some example code from this: class Boot { def selectTemplate(template: String, subPages: List[String]): RewriteResponse = { var levels

[Lift] Re: URL Rewriting - 'nested' ParsePath?

2010-02-06 Thread Alex Black
Hi Jeppe, thanks, that looks like what I need! On Feb 6, 3:03 am, Jeppe Nejsum Madsen je...@ingolfs.dk wrote: Alex Black a...@alexblack.ca writes: Hi, I'd like to rewrite a url like this: /manufacturer/product e.g.     LiftRules.statelessRewrite.append( {       case RewriteRequest(

[Lift] Re: URL Rewriting - 'nested' ParsePath?

2010-02-06 Thread Alex Black
Hi Philip, thanks for the response. That looks relevant to what i'm doing... but I think the key thing I'm looking for is for the case not to match if the product does not exist for that manufacturer, so I can show a 404. I think Jeppe's approach will work well. I'm not 100% following your

[Lift] [SOLVED] Re: lift-archetype-blank 1.1-M8 2.0-M1 : missing net.sf.retrotranslator:retrotranslator-runtime:jar:1.2.1

2010-02-06 Thread Luke Nezda
Hi, David - Thanks for your prompt response! On Feb 6, 4:45 pm, David Bernard david.bernard...@gmail.com wrote: retrotranslator-runtime version 1.2.1 is available in central repository (the default one) since 2007. see :http://repo2.maven.org/maven2/net/sf/retrotranslator/retrotranslator-...

[Lift] Lift Google Summer of Code?

2010-02-06 Thread Justin Reardon
Hi folks, I'm a Computer Science student at the University of Waterloo, looking to participate in Google Summer of Code program this spring. Have you given any thought to applying as a mentoring organization this year? I've been playing around with Lift for a while now and its been a