Re: tomcat, additional configuration needed?

[Jeroen van der Wal <je...@stromboli.it>]

I know this is an old thread but I encountered the same issue when
deploying a new application, based on the minimal archetype, on tomcat7. I
solved it by copying the hsqldb jar from /WEB-INF/lib
to  /usr/share/tomcat7/lib.

Cheers,

Jeroen



On Mon, Jan 7, 2013 at 11:49 PM, Jeroen van der Wal <je...@stromboli.it>wrote:

> Hi Christian,
>
> Indeed we tried on a Windows machine. But there Tomcat also complains
> about the offending class. I will try on Tomcat on OSX tomorrow.
>
> Thanks,
>
> Jeroen
>
>
>
> On Mon, Jan 7, 2013 at 11:35 PM, Christian Steinebach <
> Christian.Steinebach@marintek.sintef.no> wrote:
>
>> Hi,
>>
>> just for your information:
>> The problem seems to have some thing to do with Linux vs. Windows tomcat
>> installation.
>> I've tried 3 different ubuntu machines and the result is always the same.
>> :-(
>> Then I installed tomcat on a windows machine and it worked fine.
>> In all cases I used the vanilla quickstart archetype.
>> I signed up for an account at CloudBees as well, deployed, and it works
>> too...
>> I finally installed jetty on an Ubuntu machine, and the wicket viewer
>> works as well.
>>
>> In the tomcat log file before the exception, tomcat complains about
>> geronimo:
>> INFO:
>> validateJarFile(/var/lib/tomcat6/webapps/TransportPlanner/WEB-INF/lib/geronimo-servlet_2.5_spec-1.2.jar)
>> - jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
>> javax/servlet/Servlet.class
>>
>>                Christian
>>
>>
>>
>> ________________________________________
>> From: Dan Haywood [dan@haywood-associates.co.uk]
>> Sent: Monday, January 07, 2013 3:35 PM
>> To: users@isis.apache.org
>> Subject: Re: tomcat, additional configuration needed?
>>
>> Hi Christian,
>>
>> Well, now.... Jeroen and I have just generated the app from the 1.0.0
>> archetype and deployed to Tomcat (v7.0.34), and it all seems to be fine to
>> us.  And our "big" app also deploys fine.
>>
>> Not sure what to suggest next...  perhaps see if you can reproduce the
>> error from running the vanilla archetype also?
>>
>> Dan
>>
>>
>> On 7 January 2013 11:09, Christian Steinebach <
>> Christian.Steinebach@marintek.sintef.no> wrote:
>>
>> > Hi,
>> >
>> > is there anything additional configuration necessary to deploy the
>> wicket
>> > viewer to tomcat7?
>> >
>> > When trying to deploy to tomcat on localhost by copying the
>> viewer-wicket
>> > war file to webapp,
>> > tomcat throws  an exception (in localhost...log):
>> >
>> > Jan 7, 2013 11:50:42 AM org.apache.catalina.core.StandardContext
>> > filterStart
>> > SEVERE: Exception starting filter wicket
>> > com.google.inject.ProvisionException: Guice provision errors:
>> >
>> > 1) Error in custom provider, javax.jdo.JDOFatalDataStoreException: No
>> > suitable driver found for jdbc:hsqldb:mem:test
>> > NestedThrowables:
>> > java.sql.SQLException: No suitable driver found for jdbc:hsqldb:mem:test
>> >   at
>> >
>> org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:138)
>> >   at
>> >
>> org.apache.isis.core.runtime.runner.IsisInjectModule.provideIsisSystem(IsisInjectModule.java:138)
>> >   while locating org.apache.isis.core.runtime.system.IsisSystem
>> >     for field at
>> >
>> org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.system(IsisWicketApplication.java:123)
>> >   while locating app.QuickStartApplication
>> >
>> > 1 error
>> >         at
>> >
>> com.google.inject.internal.Errors.throwProvisionExceptionIfErrorsExist(Errors.java:451)
>> >         at
>> >
>> com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:65)
>> >         at
>> >
>> com.google.inject.internal.InjectorImpl.injectMembers(InjectorImpl.java:944)
>> >         at
>> >
>> org.apache.isis.viewer.wicket.viewer.IsisWicketApplication.init(IsisWicketApplication.java:191)
>> >         at
>> > org.apache.wicket.Application.initApplication(Application.java:818)
>> >         at
>> > org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:386)
>> >         at
>> > org.apache.wicket.protocol.http.WicketFilter.init(WicketFilter.java:314)
>> >         at
>> >
>> org.apache.catalina.core.ApplicationFilterConfig.initFilter(ApplicationFilterConfig.java:277)
>> >         at
>> >
>> org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:258)
>> >         at
>> >
>> org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:382)
>> >         at
>> >
>> org.apache.catalina.core.ApplicationFilterConfig.<init>(ApplicationFilterConfig.java:103)
>> >         at
>> >
>> org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:4638)
>> >         at
>> >
>> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5294)
>> >
>> >
>> > Caused by: java.sql.SQLException: No suitable driver found for
>> > jdbc:hsqldb:mem:test
>> >         at java.sql.DriverManager.getConnection(DriverManager.java:640)
>> >
>> > The applicatioin works fine with both
>> > mvn antrun:run
>> > and
>> > mvn jetty:run
>> >
>> > The hsqldb-2.2.9.jar is in the lib folder
>> >
>> > I used the quickstart archetype without any changes.
>> >
>> >          Christian
>> >
>> >
>> >
>> >
>>
>
>