[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
>>

[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(HostConfi

[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