date:20090105

[Lift] Re: Questions about User object and class

2009-01-05 Thread David Pollak

Greg,

The following compiles just fine for me:
  def wantsToKnow() : Boolean = {
var _wantsToKnow = true
this.onLogOut =  ((x: Box[User]) => _wantsToKnow = false) ::
this.onLogOut
false
  }

Is your project building against Lift 0.10-SNAPSHOT?

Thanks,

David

On Mon, Jan 5, 2009 at 3:46 PM, Meredith Gregory
wrote:

> Lifted,
>
> i'm looking at this code in 
> github.
> Lines 258 and 274 - 279 would indicate to me that an object derived from
> this class -- as i think the User object is in the std lift project
> archetype -- would be able to manipulate onLogOut. However, placing this
> code
>
> /**
>  * The singleton that has methods for accessing the database
>  */
> object User extends User with MetaMegaProtoUser[User, User with
> KeyedMetaMapper[Long, User]] {
> ...
> def wantsToKnow() : Boolean = {
> this.onLogOut = (({ x => _wantsToKnow = false}) :: this.onLogOut)
> _wantsToKnow
>   }
> ...
> }
>
> in the object's def results in this complaint
>
> [WARNING]
> /Users/lgm/work/src/projex/biosimilarity/GraphL/src/main/scala/com/biosimilarity/GraphL/model/User.scala:23:
> error: value onLogOut is not a member of object
> com.biosimilarity.GraphL.model.User
> [WARNING] this.onLogOut = (({ x => _wantsToKnow = false}) ::
> this.onLogOut)
> [WARNING]  ^
> [WARNING] one error found
> [INFO]
> 
> [ERROR] BUILD FAILURE
>
> Also, what gives with the *two* type parameters to MetaMegaProtoUser --
> which as declared in lift-util.mapper appears to take only 1 type parameter?
>
> Clueless about lift, but still sending best wishes in the New Year,
>
> --greg
>
> --
> L.G. Meredith
> Managing Partner
> Biosimilarity LLC
> 806 55th St NE
> Seattle, WA 98105
>
> +1 206.650.3740
>
> http://biosimilarity.blogspot.com
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
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 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] Questions about User object and class

2009-01-05 Thread Meredith Gregory

Lifted,

i'm looking at this code in
github.
Lines 258 and 274 - 279 would indicate to me that an object derived from
this class -- as i think the User object is in the std lift project
archetype -- would be able to manipulate onLogOut. However, placing this
code

/**
 * The singleton that has methods for accessing the database
 */
object User extends User with MetaMegaProtoUser[User, User with
KeyedMetaMapper[Long, User]] {
...
def wantsToKnow() : Boolean = {
this.onLogOut = (({ x => _wantsToKnow = false}) :: this.onLogOut)
_wantsToKnow
  }
...
}

in the object's def results in this complaint

[WARNING]
/Users/lgm/work/src/projex/biosimilarity/GraphL/src/main/scala/com/biosimilarity/GraphL/model/User.scala:23:
error: value onLogOut is not a member of object
com.biosimilarity.GraphL.model.User
[WARNING] this.onLogOut = (({ x => _wantsToKnow = false}) ::
this.onLogOut)
[WARNING]  ^
[WARNING] one error found
[INFO]

[ERROR] BUILD FAILURE

Also, what gives with the *two* type parameters to MetaMegaProtoUser --
which as declared in lift-util.mapper appears to take only 1 type parameter?

Clueless about lift, but still sending best wishes in the New Year,

--greg

-- 
L.G. Meredith
Managing Partner
Biosimilarity LLC
806 55th St NE
Seattle, WA 98105

+1 206.650.3740

http://biosimilarity.blogspot.com

--~--~-~--~~~---~--~~
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] accessing the attributes of the XML node associated with a FuncBindParam in bind(...)

2009-01-05 Thread Marc Boschma


I have been playing with the ToDo example application and having fun  
in manipulating XML.

With the  node I thought it would be good if the XHTML  
designer could pass in some guidance to the doList(...) method used in  
bind(..). ie. ...

Looking over the bind code I noticed that the attributes are not  
accessible without ending up changing the calcValue method's  
signature. I did initially try to knock up a

case class FuncWithAttrBindParam(name: String, value: (NodeSeq,  
MetaData) => NodeSeq) extends Tuple2(name, value) with BindParam

and a corresponding

case Some(ns : FuncWithAttrBindParam) =>

in in_bind(...), but it all looks like a huge kludge.

It strikes me as a little deficient to be able to utilise attributes  
within the context of a snippet and yet not within a bind. I know bind  
is quite embedded in lift now, but I think that this difference might  
prove a little frustrating. I know one solution is to just create a  
bind("todo", html,
 "exclude" ->  
ajaxCheckbox(QueryNotDone, v => {QueryNotDone(v); reDraw}),
 "list" -> doList(reDraw, false) _,
"list_singular" -> doList(reDraw, true) _)

But I think from the XHtml designer's perspective that is counter  
intuitive...

Thoughts?

--

It should be noted that this is different to the case class  
FuncAttrBindParam(name: String, value: NodeSeq => NodeSeq, newAttr:  
String) extends BindParam with BindWithAttr. Which interesting enough  
has no corresponding SuperArrowAssoc -> method match. Maybe

def ->(t: Tuple2[String, NodeSeq]) = AttrBindParam(name, t._2, t._1)
def ->(t: Tuple2[String, NodeSeq => NodeSeq]) =  
FuncAttrBindParam(name, t._2, t._1)

And maybe even...

def ->[T](t: Tuple2[String, T]) = FuncAttrBindParam(name, (name ->  
t._2).calcValue _, t._1)

or

def ->[T](t: Tuple2[String, T]) = FuncAttrBindParam(name, (t._1 ->  
t._2).calcValue _, t._1)

I'm not sure which is better on the last two... Just a thought.

Marc


--~--~-~--~~~---~--~~
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: DB/Schemifier Problem

2009-01-05 Thread David Pollak

Daniel,
Sure thing.  mvn -U clean is my friend and I hope it becomes yours too. :-)

Thanks,

David

On Mon, Jan 5, 2009 at 11:15 AM, Daniel Koller wrote:

> David,
>
> cleaning maven helped: now the Apache-SVN version compiles again and works!
>
> Thanks for your help!
>
> Kind regards,
>
> Daniel
>
>
> On Mon, Jan 5, 2009 at 5:56 PM, David Pollak <
> feeder.of.the.be...@gmail.com> wrote:
>
>> Daniel,
>>
>> Please CD into the esme/server directory.  Then type "svn update" to pull
>> the latest from the subversion repository.  Then type "mvn -U clean install"
>> (you should always do a clean install, and -U grabs the latest from the
>> Maven repositories).  Finally type "mvn jetty:run"
>>
>> Please let me know if that works.
>>
>> Thanks,
>>
>> David
>>
>> On Mon, Jan 5, 2009 at 6:57 AM, Daniel Koller wrote:
>>
>>> David,
>>>
>>> thx for your feedback. I took the version from Apache SVN,made that maven
>>> processing (which I hope takes the right versions of Scala/Lift) and created
>>> a WAR file (which I put then manually to a local Tomcat 6 install).
>>>
>>> If it helps, I can publish the used WAR file.
>>>
>>> Kind regards,
>>>
>>> Daniel
>>>
>>> On Mon, Jan 5, 2009 at 3:52 PM, David Pollak <
>>> feeder.of.the.be...@gmail.com> wrote:
>>>
 Daniel,
 It looks like there's a mis-match between the version of Scala and/or
 Lift that was used in compilation and the version that was deployed.  The
 abstract method issue is a flag for this sort of problem.

 Did you build your WAR file from scratch or did you pull it down from
 the ESME Google code project?

 Thanks,

 David


 On Sun, Jan 4, 2009 at 9:34 PM, Daniel Koller 
 wrote:

>
> Hi all,
>
> I have a problem regarding the Lift framework, where I ask for any
> helpful comments.
>
> The problem is that I access my application database, the database
> tables do obviously not exist, but they get also not created.
>
> The basic situation is like this:
> - I am working on the ESME solution, this solution has a Boot-scala
> file, which is the first called file. The relevant snippet of
> Boot.scala is:
>
> "DefaultConnectionIdentifier.jndiName = "esme"
>
>if (!DB.jndiJdbcConnAvailable_?) DB.defineConnectionManager
> (DefaultConnectionIdentifier, DBVendor)
>// where to search snippet
>LiftRules.addToPackages("us.esme")
>
>if (Props.mode == Props.RunModes.Test) {
>  Schemifier.destroyTables_!!(Log.infoF _, User, ExtSession,
>  Message, Mailbox, Tag,
>  Group, Relationship, MessageTag,
>  AuthToken, UrlStore, Tracking,
>  Action, DidPerform)
>}
>
>Schemifier.schemify(true, Log.infoF _, User, ExtSession, Message,
>Mailbox, Tag,
>Group, Relationship, MessageTag, AuthToken,
>UrlStore, Tracking, Action, DidPerform)"
>
> - During execution of Boot.scala the code breaks at at schemify-call
> with the following exception:
>
> "INFO: Deploying web application archive esme-0.2.3-SNAPSHOT.war
> ERROR - Failed to Boot
> java.lang.AbstractMethodError
>at
> net.liftweb.mapper.MetaMapper$class.$init$(MetaMapper.scala:840)
>at us.esme.model.Tag$.(Tag.scala:34)
>at us.esme.model.Tag$.(Tag.scala)
>at bootstrap.liftweb.Boot.boot(Boot.scala:59)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)
>at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
> (ClassHelpers.scala:396)
>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
> (ClassHelpers.scala:394)
>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
> (LiftRules.scala:867)
>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
> (LiftRules.scala:867)
>at net.liftweb.util.Full.map(Box.scala:282)
>at net.liftweb.http.DefaultBootstrap$.boot(LiftRules.scala:867)
>at net.liftweb.http.LiftFilter.bootLift(LiftServlet.scala:543)
>at net.liftweb.http.LiftFilter.init(LiftServlet.scala:518)
>at org.apache.catalina.core.ApplicationFilterConfig.getFilter
> (ApplicationFilterConfig.java:275)
>at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef
> (ApplicationFilterConfig.java:397)
>at org.apache.catalina.core.ApplicationFilterConfig.
> (Application

[Lift] Re: DB/Schemifier Problem

2009-01-05 Thread Daniel Koller

David,

cleaning maven helped: now the Apache-SVN version compiles again and works!

Thanks for your help!

Kind regards,

Daniel

On Mon, Jan 5, 2009 at 5:56 PM, David Pollak
wrote:

> Daniel,
>
> Please CD into the esme/server directory.  Then type "svn update" to pull
> the latest from the subversion repository.  Then type "mvn -U clean install"
> (you should always do a clean install, and -U grabs the latest from the
> Maven repositories).  Finally type "mvn jetty:run"
>
> Please let me know if that works.
>
> Thanks,
>
> David
>
> On Mon, Jan 5, 2009 at 6:57 AM, Daniel Koller wrote:
>
>> David,
>>
>> thx for your feedback. I took the version from Apache SVN,made that maven
>> processing (which I hope takes the right versions of Scala/Lift) and created
>> a WAR file (which I put then manually to a local Tomcat 6 install).
>>
>> If it helps, I can publish the used WAR file.
>>
>> Kind regards,
>>
>> Daniel
>>
>> On Mon, Jan 5, 2009 at 3:52 PM, David Pollak <
>> feeder.of.the.be...@gmail.com> wrote:
>>
>>> Daniel,
>>> It looks like there's a mis-match between the version of Scala and/or
>>> Lift that was used in compilation and the version that was deployed.  The
>>> abstract method issue is a flag for this sort of problem.
>>>
>>> Did you build your WAR file from scratch or did you pull it down from the
>>> ESME Google code project?
>>>
>>> Thanks,
>>>
>>> David
>>>
>>>
>>> On Sun, Jan 4, 2009 at 9:34 PM, Daniel Koller 
>>> wrote:
>>>

 Hi all,

 I have a problem regarding the Lift framework, where I ask for any
 helpful comments.

 The problem is that I access my application database, the database
 tables do obviously not exist, but they get also not created.

 The basic situation is like this:
 - I am working on the ESME solution, this solution has a Boot-scala
 file, which is the first called file. The relevant snippet of
 Boot.scala is:

 "DefaultConnectionIdentifier.jndiName = "esme"

if (!DB.jndiJdbcConnAvailable_?) DB.defineConnectionManager
 (DefaultConnectionIdentifier, DBVendor)
// where to search snippet
LiftRules.addToPackages("us.esme")

if (Props.mode == Props.RunModes.Test) {
  Schemifier.destroyTables_!!(Log.infoF _, User, ExtSession,
  Message, Mailbox, Tag,
  Group, Relationship, MessageTag,
  AuthToken, UrlStore, Tracking,
  Action, DidPerform)
}

Schemifier.schemify(true, Log.infoF _, User, ExtSession, Message,
Mailbox, Tag,
Group, Relationship, MessageTag, AuthToken,
UrlStore, Tracking, Action, DidPerform)"

 - During execution of Boot.scala the code breaks at at schemify-call
 with the following exception:

 "INFO: Deploying web application archive esme-0.2.3-SNAPSHOT.war
 ERROR - Failed to Boot
 java.lang.AbstractMethodError
at
 net.liftweb.mapper.MetaMapper$class.$init$(MetaMapper.scala:840)
at us.esme.model.Tag$.(Tag.scala:34)
at us.esme.model.Tag$.(Tag.scala)
at bootstrap.liftweb.Boot.boot(Boot.scala:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
 (NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
 (DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
 (ClassHelpers.scala:396)
at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
 (ClassHelpers.scala:394)
at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
 (LiftRules.scala:867)
at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
 (LiftRules.scala:867)
at net.liftweb.util.Full.map(Box.scala:282)
at net.liftweb.http.DefaultBootstrap$.boot(LiftRules.scala:867)
at net.liftweb.http.LiftFilter.bootLift(LiftServlet.scala:543)
at net.liftweb.http.LiftFilter.init(LiftServlet.scala:518)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter
 (ApplicationFilterConfig.java:275)
at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef
 (ApplicationFilterConfig.java:397)
at org.apache.catalina.core.ApplicationFilterConfig.
 (ApplicationFilterConfig.java:108)
at org.apache.catalina.core.StandardContext.filterStart
 (StandardContext.java:3709)
at org.apache.catalina.core.StandardContext.start
 (StandardContext.java:4356)
at org.apache.catalina.core.ContainerBase.addChildInternal
 (ContainerBase.java:791)

[Lift] Re: Latest snapshot docs missing mapper/record

2009-01-05 Thread Derek Chen-Becker

Doh. Red. Face. I forgot about that split...

Derek

On Mon, Jan 5, 2009 at 10:02 AM, David Pollak  wrote:

> That's because mapper and record are separate packages:
>
> http://scala-tools.org/mvnsites-snapshots/liftweb/lift-mapper/scaladocs/index.html
>
> http://scala-tools.org/mvnsites-snapshots/liftweb/lift-record/scaladocs/index.html
>
>
> On Mon, Jan 5, 2009 at 8:58 AM, Derek Chen-Becker 
> wrote:
>
>> The subject says it all. Unless this is the wrong link, of course:
>>
>>
>> http://scala-tools.org/mvnsites-snapshots/liftweb/lift-webkit/scaladocs/index.html
>>
>> Derek
>>
>>
>>
>
>
> --
> Lift, the simply functional web framework http://liftweb.net
> Collaborative Task Management http://much4.us
> 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 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: DB/Schemifier Problem

2009-01-05 Thread David Pollak

Daniel,

Please CD into the esme/server directory.  Then type "svn update" to pull
the latest from the subversion repository.  Then type "mvn -U clean install"
(you should always do a clean install, and -U grabs the latest from the
Maven repositories).  Finally type "mvn jetty:run"

Please let me know if that works.

Thanks,

David

On Mon, Jan 5, 2009 at 6:57 AM, Daniel Koller wrote:

> David,
>
> thx for your feedback. I took the version from Apache SVN,made that maven
> processing (which I hope takes the right versions of Scala/Lift) and created
> a WAR file (which I put then manually to a local Tomcat 6 install).
>
> If it helps, I can publish the used WAR file.
>
> Kind regards,
>
> Daniel
>
> On Mon, Jan 5, 2009 at 3:52 PM, David Pollak <
> feeder.of.the.be...@gmail.com> wrote:
>
>> Daniel,
>> It looks like there's a mis-match between the version of Scala and/or Lift
>> that was used in compilation and the version that was deployed.  The
>> abstract method issue is a flag for this sort of problem.
>>
>> Did you build your WAR file from scratch or did you pull it down from the
>> ESME Google code project?
>>
>> Thanks,
>>
>> David
>>
>>
>> On Sun, Jan 4, 2009 at 9:34 PM, Daniel Koller wrote:
>>
>>>
>>> Hi all,
>>>
>>> I have a problem regarding the Lift framework, where I ask for any
>>> helpful comments.
>>>
>>> The problem is that I access my application database, the database
>>> tables do obviously not exist, but they get also not created.
>>>
>>> The basic situation is like this:
>>> - I am working on the ESME solution, this solution has a Boot-scala
>>> file, which is the first called file. The relevant snippet of
>>> Boot.scala is:
>>>
>>> "DefaultConnectionIdentifier.jndiName = "esme"
>>>
>>>if (!DB.jndiJdbcConnAvailable_?) DB.defineConnectionManager
>>> (DefaultConnectionIdentifier, DBVendor)
>>>// where to search snippet
>>>LiftRules.addToPackages("us.esme")
>>>
>>>if (Props.mode == Props.RunModes.Test) {
>>>  Schemifier.destroyTables_!!(Log.infoF _, User, ExtSession,
>>>  Message, Mailbox, Tag,
>>>  Group, Relationship, MessageTag,
>>>  AuthToken, UrlStore, Tracking,
>>>  Action, DidPerform)
>>>}
>>>
>>>Schemifier.schemify(true, Log.infoF _, User, ExtSession, Message,
>>>Mailbox, Tag,
>>>Group, Relationship, MessageTag, AuthToken,
>>>UrlStore, Tracking, Action, DidPerform)"
>>>
>>> - During execution of Boot.scala the code breaks at at schemify-call
>>> with the following exception:
>>>
>>> "INFO: Deploying web application archive esme-0.2.3-SNAPSHOT.war
>>> ERROR - Failed to Boot
>>> java.lang.AbstractMethodError
>>>at
>>> net.liftweb.mapper.MetaMapper$class.$init$(MetaMapper.scala:840)
>>>at us.esme.model.Tag$.(Tag.scala:34)
>>>at us.esme.model.Tag$.(Tag.scala)
>>>at bootstrap.liftweb.Boot.boot(Boot.scala:59)
>>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>at sun.reflect.NativeMethodAccessorImpl.invoke
>>> (NativeMethodAccessorImpl.java:39)
>>>at sun.reflect.DelegatingMethodAccessorImpl.invoke
>>> (DelegatingMethodAccessorImpl.java:25)
>>>at java.lang.reflect.Method.invoke(Method.java:597)
>>>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
>>> (ClassHelpers.scala:396)
>>>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
>>> (ClassHelpers.scala:394)
>>>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
>>> (LiftRules.scala:867)
>>>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
>>> (LiftRules.scala:867)
>>>at net.liftweb.util.Full.map(Box.scala:282)
>>>at net.liftweb.http.DefaultBootstrap$.boot(LiftRules.scala:867)
>>>at net.liftweb.http.LiftFilter.bootLift(LiftServlet.scala:543)
>>>at net.liftweb.http.LiftFilter.init(LiftServlet.scala:518)
>>>at org.apache.catalina.core.ApplicationFilterConfig.getFilter
>>> (ApplicationFilterConfig.java:275)
>>>at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef
>>> (ApplicationFilterConfig.java:397)
>>>at org.apache.catalina.core.ApplicationFilterConfig.
>>> (ApplicationFilterConfig.java:108)
>>>at org.apache.catalina.core.StandardContext.filterStart
>>> (StandardContext.java:3709)
>>>at org.apache.catalina.core.StandardContext.start
>>> (StandardContext.java:4356)
>>>at org.apache.catalina.core.ContainerBase.addChildInternal
>>> (ContainerBase.java:791)
>>>at
>>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:
>>> 771)
>>>at
>>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:
>>> 525)
>>>at
>>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:
>>> 829)
>>>at
>>> org.apache.catalina.start

[Lift] Re: Latest snapshot docs missing mapper/record

2009-01-05 Thread David Pollak

That's because mapper and record are separate packages:
http://scala-tools.org/mvnsites-snapshots/liftweb/lift-mapper/scaladocs/index.html
http://scala-tools.org/mvnsites-snapshots/liftweb/lift-record/scaladocs/index.html

On Mon, Jan 5, 2009 at 8:58 AM, Derek Chen-Becker wrote:

> The subject says it all. Unless this is the wrong link, of course:
>
>
> http://scala-tools.org/mvnsites-snapshots/liftweb/lift-webkit/scaladocs/index.html
>
> Derek
>
> >
>


-- 
Lift, the simply functional web framework http://liftweb.net
Collaborative Task Management http://much4.us
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 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] Latest snapshot docs missing mapper/record

2009-01-05 Thread Derek Chen-Becker

The subject says it all. Unless this is the wrong link, of course:

http://scala-tools.org/mvnsites-snapshots/liftweb/lift-webkit/scaladocs/index.html

Derek

--~--~-~--~~~---~--~~
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: DB/Schemifier Problem

2009-01-05 Thread Daniel Koller

David,

thx for your feedback. I took the version from Apache SVN,made that maven
processing (which I hope takes the right versions of Scala/Lift) and created
a WAR file (which I put then manually to a local Tomcat 6 install).

If it helps, I can publish the used WAR file.

Kind regards,

Daniel

On Mon, Jan 5, 2009 at 3:52 PM, David Pollak
wrote:

> Daniel,
> It looks like there's a mis-match between the version of Scala and/or Lift
> that was used in compilation and the version that was deployed.  The
> abstract method issue is a flag for this sort of problem.
>
> Did you build your WAR file from scratch or did you pull it down from the
> ESME Google code project?
>
> Thanks,
>
> David
>
>
> On Sun, Jan 4, 2009 at 9:34 PM, Daniel Koller wrote:
>
>>
>> Hi all,
>>
>> I have a problem regarding the Lift framework, where I ask for any
>> helpful comments.
>>
>> The problem is that I access my application database, the database
>> tables do obviously not exist, but they get also not created.
>>
>> The basic situation is like this:
>> - I am working on the ESME solution, this solution has a Boot-scala
>> file, which is the first called file. The relevant snippet of
>> Boot.scala is:
>>
>> "DefaultConnectionIdentifier.jndiName = "esme"
>>
>>if (!DB.jndiJdbcConnAvailable_?) DB.defineConnectionManager
>> (DefaultConnectionIdentifier, DBVendor)
>>// where to search snippet
>>LiftRules.addToPackages("us.esme")
>>
>>if (Props.mode == Props.RunModes.Test) {
>>  Schemifier.destroyTables_!!(Log.infoF _, User, ExtSession,
>>  Message, Mailbox, Tag,
>>  Group, Relationship, MessageTag,
>>  AuthToken, UrlStore, Tracking,
>>  Action, DidPerform)
>>}
>>
>>Schemifier.schemify(true, Log.infoF _, User, ExtSession, Message,
>>Mailbox, Tag,
>>Group, Relationship, MessageTag, AuthToken,
>>UrlStore, Tracking, Action, DidPerform)"
>>
>> - During execution of Boot.scala the code breaks at at schemify-call
>> with the following exception:
>>
>> "INFO: Deploying web application archive esme-0.2.3-SNAPSHOT.war
>> ERROR - Failed to Boot
>> java.lang.AbstractMethodError
>>at net.liftweb.mapper.MetaMapper$class.$init$(MetaMapper.scala:840)
>>at us.esme.model.Tag$.(Tag.scala:34)
>>at us.esme.model.Tag$.(Tag.scala)
>>at bootstrap.liftweb.Boot.boot(Boot.scala:59)
>>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>at sun.reflect.NativeMethodAccessorImpl.invoke
>> (NativeMethodAccessorImpl.java:39)
>>at sun.reflect.DelegatingMethodAccessorImpl.invoke
>> (DelegatingMethodAccessorImpl.java:25)
>>at java.lang.reflect.Method.invoke(Method.java:597)
>>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
>> (ClassHelpers.scala:396)
>>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
>> (ClassHelpers.scala:394)
>>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
>> (LiftRules.scala:867)
>>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
>> (LiftRules.scala:867)
>>at net.liftweb.util.Full.map(Box.scala:282)
>>at net.liftweb.http.DefaultBootstrap$.boot(LiftRules.scala:867)
>>at net.liftweb.http.LiftFilter.bootLift(LiftServlet.scala:543)
>>at net.liftweb.http.LiftFilter.init(LiftServlet.scala:518)
>>at org.apache.catalina.core.ApplicationFilterConfig.getFilter
>> (ApplicationFilterConfig.java:275)
>>at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef
>> (ApplicationFilterConfig.java:397)
>>at org.apache.catalina.core.ApplicationFilterConfig.
>> (ApplicationFilterConfig.java:108)
>>at org.apache.catalina.core.StandardContext.filterStart
>> (StandardContext.java:3709)
>>at org.apache.catalina.core.StandardContext.start
>> (StandardContext.java:4356)
>>at org.apache.catalina.core.ContainerBase.addChildInternal
>> (ContainerBase.java:791)
>>at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:
>> 771)
>>at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:
>> 525)
>>at
>> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:
>> 829)
>>at
>> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:
>> 718)
>>at
>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:
>> 490)
>>at
>> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
>>at org.apache.catalina.startup.HostConfig.lifecycleEvent
>> (HostConfig.java:311)
>>at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
>> (LifecycleSupport.java:117)
>>at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
>> 1053)
>>at
>> org.apache.catalina.core.S

[Lift] Re: DB/Schemifier Problem

2009-01-05 Thread David Pollak

Daniel,
It looks like there's a mis-match between the version of Scala and/or Lift
that was used in compilation and the version that was deployed.  The
abstract method issue is a flag for this sort of problem.

Did you build your WAR file from scratch or did you pull it down from the
ESME Google code project?

Thanks,

David

On Sun, Jan 4, 2009 at 9:34 PM, Daniel Koller wrote:

>
> Hi all,
>
> I have a problem regarding the Lift framework, where I ask for any
> helpful comments.
>
> The problem is that I access my application database, the database
> tables do obviously not exist, but they get also not created.
>
> The basic situation is like this:
> - I am working on the ESME solution, this solution has a Boot-scala
> file, which is the first called file. The relevant snippet of
> Boot.scala is:
>
> "DefaultConnectionIdentifier.jndiName = "esme"
>
>if (!DB.jndiJdbcConnAvailable_?) DB.defineConnectionManager
> (DefaultConnectionIdentifier, DBVendor)
>// where to search snippet
>LiftRules.addToPackages("us.esme")
>
>if (Props.mode == Props.RunModes.Test) {
>  Schemifier.destroyTables_!!(Log.infoF _, User, ExtSession,
>  Message, Mailbox, Tag,
>  Group, Relationship, MessageTag,
>  AuthToken, UrlStore, Tracking,
>  Action, DidPerform)
>}
>
>Schemifier.schemify(true, Log.infoF _, User, ExtSession, Message,
>Mailbox, Tag,
>Group, Relationship, MessageTag, AuthToken,
>UrlStore, Tracking, Action, DidPerform)"
>
> - During execution of Boot.scala the code breaks at at schemify-call
> with the following exception:
>
> "INFO: Deploying web application archive esme-0.2.3-SNAPSHOT.war
> ERROR - Failed to Boot
> java.lang.AbstractMethodError
>at net.liftweb.mapper.MetaMapper$class.$init$(MetaMapper.scala:840)
>at us.esme.model.Tag$.(Tag.scala:34)
>at us.esme.model.Tag$.(Tag.scala)
>at bootstrap.liftweb.Boot.boot(Boot.scala:59)
>at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:39)
>at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:25)
>at java.lang.reflect.Method.invoke(Method.java:597)
>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
> (ClassHelpers.scala:396)
>at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
> (ClassHelpers.scala:394)
>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
> (LiftRules.scala:867)
>at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
> (LiftRules.scala:867)
>at net.liftweb.util.Full.map(Box.scala:282)
>at net.liftweb.http.DefaultBootstrap$.boot(LiftRules.scala:867)
>at net.liftweb.http.LiftFilter.bootLift(LiftServlet.scala:543)
>at net.liftweb.http.LiftFilter.init(LiftServlet.scala:518)
>at org.apache.catalina.core.ApplicationFilterConfig.getFilter
> (ApplicationFilterConfig.java:275)
>at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef
> (ApplicationFilterConfig.java:397)
>at org.apache.catalina.core.ApplicationFilterConfig.
> (ApplicationFilterConfig.java:108)
>at org.apache.catalina.core.StandardContext.filterStart
> (StandardContext.java:3709)
>at org.apache.catalina.core.StandardContext.start
> (StandardContext.java:4356)
>at org.apache.catalina.core.ContainerBase.addChildInternal
> (ContainerBase.java:791)
>at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:
> 771)
>at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:
> 525)
>at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:
> 829)
>at
> org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:
> 718)
>at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:
> 490)
>at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
>at org.apache.catalina.startup.HostConfig.lifecycleEvent
> (HostConfig.java:311)
>at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
> (LifecycleSupport.java:117)
>at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
> 1053)
>at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
>at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
> 1045)
>at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:
> 443)
>at org.apache.catalina.core.StandardService.start
> (StandardService.java:516)
>at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:
> 710)
>at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
>at sun

[Lift] DB/Schemifier Problem

2009-01-05 Thread Daniel Koller


Hi all,

I have a problem regarding the Lift framework, where I ask for any
helpful comments.

The problem is that I access my application database, the database
tables do obviously not exist, but they get also not created.

The basic situation is like this:
- I am working on the ESME solution, this solution has a Boot-scala
file, which is the first called file. The relevant snippet of
Boot.scala is:

"DefaultConnectionIdentifier.jndiName = "esme"

if (!DB.jndiJdbcConnAvailable_?) DB.defineConnectionManager
(DefaultConnectionIdentifier, DBVendor)
// where to search snippet
LiftRules.addToPackages("us.esme")

if (Props.mode == Props.RunModes.Test) {
  Schemifier.destroyTables_!!(Log.infoF _, User, ExtSession,
  Message, Mailbox, Tag,
  Group, Relationship, MessageTag,
  AuthToken, UrlStore, Tracking,
  Action, DidPerform)
}

Schemifier.schemify(true, Log.infoF _, User, ExtSession, Message,
Mailbox, Tag,
Group, Relationship, MessageTag, AuthToken,
UrlStore, Tracking, Action, DidPerform)"

- During execution of Boot.scala the code breaks at at schemify-call
with the following exception:

"INFO: Deploying web application archive esme-0.2.3-SNAPSHOT.war
ERROR - Failed to Boot
java.lang.AbstractMethodError
at net.liftweb.mapper.MetaMapper$class.$init$(MetaMapper.scala:840)
at us.esme.model.Tag$.(Tag.scala:34)
at us.esme.model.Tag$.(Tag.scala)
at bootstrap.liftweb.Boot.boot(Boot.scala:59)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
(ClassHelpers.scala:396)
at net.liftweb.util.ClassHelpers$$anonfun$createInvoker$1.apply
(ClassHelpers.scala:394)
at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
(LiftRules.scala:867)
at net.liftweb.http.DefaultBootstrap$$anonfun$boot$1.apply
(LiftRules.scala:867)
at net.liftweb.util.Full.map(Box.scala:282)
at net.liftweb.http.DefaultBootstrap$.boot(LiftRules.scala:867)
at net.liftweb.http.LiftFilter.bootLift(LiftServlet.scala:543)
at net.liftweb.http.LiftFilter.init(LiftServlet.scala:518)
at org.apache.catalina.core.ApplicationFilterConfig.getFilter
(ApplicationFilterConfig.java:275)
at org.apache.catalina.core.ApplicationFilterConfig.setFilterDef
(ApplicationFilterConfig.java:397)
at org.apache.catalina.core.ApplicationFilterConfig.
(ApplicationFilterConfig.java:108)
at org.apache.catalina.core.StandardContext.filterStart
(StandardContext.java:3709)
at org.apache.catalina.core.StandardContext.start
(StandardContext.java:4356)
at org.apache.catalina.core.ContainerBase.addChildInternal
(ContainerBase.java:791)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:
771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:
525)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:
829)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:
718)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:
490)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1147)
at org.apache.catalina.startup.HostConfig.lifecycleEvent
(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
(LifecycleSupport.java:117)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:
1045)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:
443)
at org.apache.catalina.core.StandardService.start
(StandardService.java:516)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:
710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:578)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
05.01.2009 06:49:05 org.apache.coyote.http11.Http11Protocol start
INFO: Starting Coy

[Lift] Re: Flot widget

2009-01-05 Thread Francois Bertrand


> Also, I'd like to do some code cleanup (e.g., changing Option to Box) in the
> flot widget.  Is that okay?

Yes, it is OK.

Any other suggestions are welcome


--~--~-~--~~~---~--~~
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: Questions about User object and class

[Lift] Questions about User object and class

[Lift] accessing the attributes of the XML node associated with a FuncBindParam in bind(...)

[Lift] Re: DB/Schemifier Problem

[Lift] Re: DB/Schemifier Problem

[Lift] Re: Latest snapshot docs missing mapper/record

[Lift] Re: DB/Schemifier Problem

[Lift] Re: Latest snapshot docs missing mapper/record

[Lift] Latest snapshot docs missing mapper/record

[Lift] Re: DB/Schemifier Problem

[Lift] Re: DB/Schemifier Problem

[Lift] DB/Schemifier Problem

[Lift] Re: Flot widget

13 matches

Site Navigation

Mail list logo

Footer information