ooh, I feel so bad... :)
I knew it was something very stupid - I did not run
the 'maven quickStart'. For some reason I thought it
was intended for the HSQLDB only...

Sorry for wasting so much of your time!

Thanks, Randy,
Marina

--- [EMAIL PROTECTED] wrote:

> Marina:
> 
> If your j2 DB is not setup, nothing will work
> anyway, so we are back to
> the failing maven build... you did use "maven
> quickStart", no?
> 
> Also, your DB URL probably needs to be
> 
> jdbc:mysql://127.0.0.1:3306/j2
> 
> or
> 
> jdbc:mysql://localhost/j2,
> 
> (mysql can be picky about IP usage and I am not sure
> about the port you
> specified).
> 
> Randy
> 
> > Thanks, Randy :)
> > I modified jetspeed.xml file using the one from a
> > working HSQL J2M2 installation as an example and
> > copied it into the
> > <TOMCAT_HOME>/conf/Catalina/localhost dir.
> > I also copied a security.xml file from the HSQLDB
> J2M2
> > installation and adjusted the docBase value.
> >
> > Unfortunately, when I started Tomcat, I've got the
> > same error:
> >
> > Caused by:
> > org.apache.jetspeed.prefs.PreferencesException:
> Failed
> > to initialize prefs
> >
>
api.org.springframework.transaction.CannotCreateTransactionException:
> > Could not create OJB transaction; nested exception
> is
> > org.apache.ojb.broker.accesslayer.LookupException:
> > SQLException thrown while trying to get Connection
> > from Datasource (java:comp/env/jdbc/jetspeed) at
> >
>
org.apache.jetspeed.prefs.impl.PreferencesFactoryImpl.init(Preference
> > sFactoryImpl.java:70) at
> >
>
sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)
> > at
> >
>
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> > ...
> >
> > And in the J2's log file:
> > 2005-02-27 18:24:24
> >
> StandardContext[/jetspeed]StandardWrapper.Throwable
> > java.lang.NullPointerException
> >     at
> >
>
org.apache.jetspeed.velocity.JetspeedVelocityViewServlet.init(JetspeedVelocityViewServlet.java:137)
> >     at
> >
>
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1044)
> >     at
> >
>
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:876)
> >     at
> >
> >
> > One thing that puzzles me (among others, of
> course) is
> > that the 'j2' DB did not get populated while
> 'j2test'
> > did...
> >
> > Here is my jetspeed.xml - lines that I changed:
> >     <!-- HSQL dB username and password for dB
> > connections  -->
> >     <parameter>
> >      <name>username</name>
> >      <value>admin</value>
> >     </parameter>
> >     <parameter>
> >      <name>password</name>
> >      <value>admin</value>
> >     </parameter>
> >
> >     <!-- Class name for HSQL JDBC driver -->
> >     <parameter>
> >        <name>driverClassName</name>
> >        <value>org.gjt.mm.mysql.Driver</value>
> >     </parameter>
> >
> >     <!-- The JDBC connection url for connecting to
> > your HSQL dB.  -->
> >     <parameter>
> >       <name>url</name>
> >       <value>jdbc:mysql://127.0.0.1:3306</value>
> >     </parameter>
> >   </ResourceParams>
> >
> > Thanks for looking into this!
> > Marina
> >
> > --- [EMAIL PROTECTED] wrote:
> >
> >> Marina,
> >>
> >> > 3. jetspeed.xml
> >> > there was no jetspeed.xml in the
> >> > =<TOMCAT_HOME>/conf/Catalina/localhost dir
> >> > The only jetspeed.xml files in the
> J2-project-home
> >> > directory that I found were:
> >> >
> >>
> >
>
maven-plugin/target/classes/plugin-resources/jetspeed.xml
> >> > portal/src/resources/jetspeed.xml
> >> > Should I manually edit one of them and copy
> into
> >> > <TOMCAT_HOME>/conf/Catalina/localhost dir ?
> >>
> >> Since you manually copied the jetspeed.war into
> >> webapps, I assume you will
> >> need to do the same thing with the
> >> portal/src/resources/jetspeed.xml file.
> >> It is certainly simple enough to try!
> >>
> >> > Is not it supposed to be done by the maven
> >> 'allBuild'
> >> > goal?
> >>
> >> Well, so is copying jetspeed.war into webapps! :)
> >> Something is broken for
> >> sure, but I am just interesting in seeing if you
> can
> >> get it to run at all
> >> since you have taken it almost this far already.
> >> Yes, we are in the weeds
> >> at this point!
> >>
> >> Randy
> >>
> >>
> >>
> >
>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> >> [EMAIL PROTECTED]
> >> For additional commands, e-mail:
> >> [EMAIL PROTECTED]
> >>
> >>
> >
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> [EMAIL PROTECTED]
> >
> >
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to