Scala is very, very, super ultra mega version fragile.  This means that code
compiled with 2.7.5 will not work with code compiled with 2.7.7 and vice
versa.

So, in your pom.xml file, please set your scala version to 2.7.5 (nothing
else... not 2.7.4, not 2.7.7) and lift to 1.0.2

Then mvn clean tomcat:run -- does it work?

Then mvn clean install -- does the WAR file work in Tomcat?

On Thu, Nov 12, 2009 at 1:10 PM, DavidV <[email protected]> wrote:

>
> Another potentially helpful detail is that I get the same liftFilter
> error when running on a local jetty server through maven as I do when
> running on tomcat (also through maven).  I am executing a clean
> command before running the web app each and every time.
>
> ...
> 2009-11-12 16:10:05.833::WARN:  failed LiftFilter:
> java.lang.AbstractMethodError
>
> 2009-11-12 16:10:05.834::WARN:  failed
> org.mortbay.jetty.plugin.Jetty6PluginWebA
> ppcont...@14c0275{/,C:\Source\trunk\eclipse\testLift\src\main\webapp}:
> java.lang
> .AbstractMethodError
> ...
>
>
>
> On Nov 12, 3:40 pm, DavidV <[email protected]> wrote:
> > I just tried to run the same code that used to work with Lift-1.0.1
> > and Scala 2.7.5 with my updates to Lift 1.0.1 and Scala 2.7.7 and I
> > got the following error:
> >
> > [INFO] [tomcat:run {execution: default-cli}]
> > [INFO] Running war onhttp://localhost:8080/portal
> > [INFO] Creating Tomcat server configuration at c:\Source\trunk\eclipse
> > \testLift\
> > target\tomcat
> > Nov 12, 2009 3:36:51 PM org.apache.catalina.startup.Embedded start
> > INFO: Starting tomcat server
> > Nov 12, 2009 3:36:51 PM org.apache.catalina.core.StandardEngine start
> > INFO: Starting Servlet Engine: Apache Tomcat/6.0.16
> > Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext
> > filterStart
> > SEVERE: Exception starting filterLiftFilter
> > java.lang.AbstractMethodError
> >         at scala.actors.Scheduler$.impl(Scheduler.scala:35)
> >         at scala.actors.Scheduler$.execute(Scheduler.scala:101)
> >         at scala.actors.Actor$class.start(Actor.scala:783)
> >         at net.liftweb.http.PointlessActorToWorkAroundBug$.start
> > (LiftServlet.sca
> > la:702)
> >         at net.liftweb.http.PointlessActorToWorkAroundBug$.ctor
> > (LiftServlet.scal
> > a:767)
> >         at net.liftweb.http.PointlessActorToWorkAroundBug$.<init>
> > (LiftServlet.sc
> > ala:776)
> >         at net.liftweb.http.PointlessActorToWorkAroundBug$.<clinit>
> > (LiftServlet.
> > scala)
> >         at net.liftweb.http.LiftFilter.init(LiftServlet.scala:563)
> >         at org.apache.catalina.core.ApplicationFilterConfig.getFilter
> > (Applicatio
> > nFilterConfig.java:275)
> >         at
> > org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(Applica
> > tionFilterConfig.java:397)
> >         at org.apache.catalina.core.ApplicationFilterConfig.<init>
> > (ApplicationFi
> > lterConfig.java:108)
> >         at org.apache.catalina.core.StandardContext.filterStart
> > (StandardContext.
> > java:3709)
> >         at org.apache.catalina.core.StandardContext.start
> > (StandardContext.java:4
> > 356)
> >         at org.apache.catalina.core.ContainerBase.start
> > (ContainerBase.java:1045)
> >
> >         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.startup.Embedded.start(Embedded.java:
> > 825)
> >         at org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer
> > (AbstractRunMo
> > jo.java:385)
> >         at org.codehaus.mojo.tomcat.AbstractRunMojo.execute
> > (AbstractRunMojo.java
> > :144)
> >         at org.apache.maven.plugin.DefaultPluginManager.executeMojo
> > (DefaultPlugi
> > nManager.java:490)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> > ultLifecycleExecutor.java:694)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone
> > Goal(DefaultLifecycleExecutor.java:569)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> > ltLifecycleExecutor.java:539)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> > dleFailures(DefaultLifecycleExecutor.java:387)
> >         at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> > ts(DefaultLifecycleExecutor.java:348)
> >         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute
> > (DefaultLi
> > fecycleExecutor.java:180)
> >         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:
> > 328)
> >         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:
> > 138)
> >         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> >         at org.apache.maven.cli.compat.CompatibleMain.main
> > (CompatibleMain.java:6
> > 0)
> >         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >         at sun.reflect.NativeMethodAccessorImpl.invoke
> > (NativeMethodAccessorImpl.
> > java:39)
> >         at sun.reflect.DelegatingMethodAccessorImpl.invoke
> > (DelegatingMethodAcces
> > sorImpl.java:25)
> >         at java.lang.reflect.Method.invoke(Method.java:597)
> >         at org.codehaus.classworlds.Launcher.launchEnhanced
> > (Launcher.java:315)
> >         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >         at org.codehaus.classworlds.Launcher.mainWithExitCode
> > (Launcher.java:430)
> >
> >         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> > Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext start
> > SEVERE: Error filterStart
> > Nov 12, 2009 3:36:53 PM org.apache.catalina.core.StandardContext start
> > SEVERE: Context [/portal] startupfaileddue to previous errors
> > Nov 12, 2009 3:36:53 PM org.apache.coyote.http11.Http11Protocol init
> > INFO: Initializing Coyote HTTP/1.1 on http-8080
> > Nov 12, 2009 3:36:54 PM org.apache.coyote.http11.Http11Protocol start
> > INFO: Starting Coyote HTTP/1.1 on http-8080
> >
> > This seems more consistent with whatever is happening on the external
> > tomcat server...
> > Thoughts?  Also, any ideas about the test failures during the mvn
> > clean package command?
> >
> > Thanks, I finally feel like I'm getting somewhere now!
> > -David
> >
> > On Nov 12, 3:21 pm, DavidV <[email protected]> wrote:
> >
> > > On a side note, while I'm installing Lift 1.0.2 with Scala2.7.5, I
> > > always execute a "clean" command before the mvn package.  However, I
> > > also need to execute a "clean" in eclipse before the mvn package works
> > > properly.  Otherwise, I get this error:
> >
> > > -------------------------------------------------------
> > >  T E S T S
> > > -------------------------------------------------------
> > > Running net.genomas.lift.test.AppTest
> > > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 1.258
> > > sec <<< FA
> > > ILURE!
> >
> > > Results :
> >
> > > Tests in error:
> > >   testXml(net.genomas.lift.test.AppTest)
> >
> > > Tests run: 2, Failures: 0, Errors: 1, Skipped: 0
> >
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [ERROR] BUILD FAILURE
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] There are test failures.
> >
> > > Please refer to c:\Source\trunk\eclipse\testLift\target\surefire-
> > > reports for the
> > >  individual test results.
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] For more information, run Maven with the -e switch
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> > > [INFO] Total time: 32 seconds
> > > [INFO] Finished at: Thu Nov 12 15:21:06 EST 2009
> > > [INFO] Final Memory: 29M/53M
> > > [INFO]
> > >
> ------------------------------------------------------------------------
> >
> > > I now have Lift-1.0.2 and Scala 2.7.7 and am testing with tomcat.
> >
> > > On Nov 12, 2:43 pm, David Pollak <[email protected]>
> > > wrote:
> >
> > > > On Thu, Nov 12, 2009 at 11:36 AM, DavidV <[email protected]>
> wrote:
> >
> > > > > I don't appear to have any conflicting jars in my
> TOMCAT_HOME/common/
> > > > > lib folder, however, I am now realizing that I have a postgres
> > > > > jdbc3 .jar file in there and I am using a jdbc4 .jar postres file
> in
> > > > > my webapp.  Perhaps that is the problem?  I'll check that out.
> >
> > > > > I am using Lift 1.0.1 with Scala version 2.7.5
> >
> > > > Please use Lift 1.0.2
> >
> > > > Please delete ~/.m2 (or whereever your Maven repository is)
> >
> > > > Please do a "mvn clean install"
> >
> > > > Then test locally (mvn tomcat:run)  If it works, copy to your other
> Tomcat
> > > > instance and see how things work.
> >
> > > > > It does work with the tomcat on my computer, which leads me to
> believe
> > > > > that it should be compatible with the current versions of
> Lift/Scala
> > > > > that I'm using.  Maybe that's an incorrect assumption though, as
> I'm
> > > > > not very familiar with tomcat.
> >
> > > > > On Nov 12, 2:15 pm, David Pollak <[email protected]>
> > > > > wrote:
> > > > > > What version of Lift are you using?
> >
> > > > > > If it's Lift 1.1-M7 or 1.1-SNAPSHOT, please make sure you've got
> the
> > > > > Scala
> > > > > > version set to 2.7.7
> >
> > > > > > If you're using Eclipse for development, please make sure to do a
> mvn
> > > > > *clean
> > > > > > * package to build your WAR file.  The clean phase is super
> important.
> >
> > > > > > On Thu, Nov 12, 2009 at 11:07 AM, DavidV <
> [email protected]>
> > > > > wrote:
> >
> > > > > > > I am having some issues deploying my Lift web application to a
> tomcat
> > > > > > > server.
> > > > > > > When I run tomcat through maven (mvn tomcat:run), the web
> application
> > > > > > > works properly and connects to my postgres database.  However,
> when I
> > > > > > > use mvn package to create a war file which I then deploy to a
> local
> > > > > > > tomcat server (on my computer) only the HTML of the web
> application
> > > > > > > appears and the snippets with the application's content fail.
>  It
> > > > > > > appears to be a problem with the sitemap loading properly,
> because I
> > > > > > > changed the sitemap by deleting one of many Loc.If parameters
> and the
> > > > > > > web application then worked as expected.  However, when I then
> tried
> > > > > > > to deploy the same .war file to a tomcat server on a different
> > > > > > > computer, the web appfailedagain, showing only the HTML and not
> the
> > > > > > > snippets.  I suspect that perhaps this is because I need to
> change my
> > > > > > > url to the postgres database, but I've tried many permutations
> of the
> > > > > > > url and none seem to work.
> > > > > > > To make things worse, the logging doesn't seem to be working
> properly
> > > > > > > making it difficult to diagnose the exact problem.  I can't
> locate a
> > > > > > > stdout.log file anywhere.  In my catalina.out file I get the
> following
> > > > > > > error:
> >
> > > > > > > java.lang.NullPointerException
> > > > > > >        at scala.runtime.BoxesRunTime.boxToInteger(Unknown
> Source)
> > > > > > >        at
> scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply
> > > > > > > (Actor.scala:800)
> > > > > > >        at
> scala.actors.Actor$$anonfun$scala$actors$Actor$$seq$1.apply
> > > > > > > (Actor.scala:794)
> > > > > > >        at scala.actors.Reaction.run(Reaction.scala:82)
> > > > > > >        at
> >
> > ...
> >
> > read more ยป
> >
>


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

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