FYI - I have deployed agains tomcat-4.1.29 (as is used by Scott) and had NO
datasource issues. Oddly, if I press refresh on my browser, I get various
flavors of the screen: sometimes nothing, sometimes just the jetspeed logo,
and sometimes portelts for hello, goodbye, customerlist (empty), preferences
portlet (empty) and another. The non empty portlets contain debug type
info - is this the current state of jetspeed2? Or do I still have
installation issues to address.
Below is my working with Tomcat5 for anyone who is trying the same:
The Tomcat5 documentation was not clear if the META-INF was in CATALINA_HOME
or the webapp directory. Anyway, I tried renaming jetspeed.xml to
context.xml in the following locations:
- [tomcat]/META-INF/context.xml
- [tomcat]/webapps/META-INF/context.xml
- [tomcat]/webapps/jetspeed/META-INF/context.xml
None of these fixed the error.
I next took the suggestion of Jeremy Ford and looked for manager.xml and
admin.xml. Both were found in
- [tomcat]/conf/Catalina/localhost
- [tomcat]/server/webapps/admin/admin.xml (similar path for
manager.xml).
So, I placed the jetspeed.xml in [tomcat]/conf/Catalina/localhost and the
connection error is gone! However calling localhost:8080/jetspeed is a white
screen with the following in Catalina.out.
DEBUG:
PortletContainerImpl.portletService(PortletApplicationBrowser:41:PAM::Portle
tApplicationBrowser) called.
ApplicationBrowserPortlet: initializing portlet, config =
PortletApplicationBrowser
[MHL] Ready for action...
Mar 17, 2004 11:24:00 AM org.apache.jasper.runtime.JspFactoryImpl
internalGetPageContext
SEVERE: Exception initializing page context
java.lang.NullPointerException
at
org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRe
quest.java:546)
at
javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWr
apper.java:260)
at
org.apache.catalina.core.ApplicationHttpRequest.getSession(ApplicationHttpRe
quest.java:534)
[bunch of stuff deleted here]
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.
java:750)
at
org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatch
er.java:636)
at
org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher
.java:546)
at
org.apache.jetspeed.dispatcher.JetspeedRequestDispatcher.include(JetspeedReq
uestDispatcher.java:63)
at
org.apache.jetspeed.demo.preferences.PreferencePortlet.doView(PreferencePort
let.java:53)
Like on Tomcat 4.1.29, if I press refresh on my browser, the above error
goes away, and I get various amounts of screen content on each refresh. At
best, I get less content on the screen compare to Tomcat4 - for example, I
never see content in the CustomerList nor the Preferences portlets in
Tomcat5, while on Tomcat4, I do sometimes get this data.
As this is in development, I did not expect a fully functional app. I just
wanted to see the current status and perhaps where I could contribute. So,
is the behavior I am seeing the current status, or do I still have install
issues which I need to resolve before I start?
Thanks!
Steve B.
----- Original Message -----
From: "Weaver, Scott" <[EMAIL PROTECTED]>
To: "'Jetspeed Users List'" <[EMAIL PROTECTED]>
Sent: Wednesday, March 17, 2004 9:33 AM
Subject: RE: Jetspeed2 cannot connect to datasource
> Hi Steve,
>
> It looks like you will need to create a /META-INF directory off the root
of
> the webapp, copy jetspeed.xml to it and rename is context.xml. I haven't
> tried this, but this how the docs for Tomcat 5 say you should do this.
Let
> me know if this works and I will add it to the build.
>
> I got the information from here:
> http://jakarta.apache.org/tomcat/tomcat-5.0-doc/appdev/deployment.html
>
>
> Regards,
> *================================*
> | Scott T Weaver |
> | <[EMAIL PROTECTED]> |
> | Apache Jetspeed Portal Project |
> | Apache Pluto Portlet Container |
> *================================*
>
> > -----Original Message-----
> > From: Jeremy Ford [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, March 16, 2004 11:22 PM
> > To: 'Jetspeed Users List'
> > Subject: RE: Jetspeed2 cannot connect to datasource
> >
> > I seem to remember seeing xml files similar to the Jetspeed.xml file
being
> > placed in a different location under tomcat 5.X. You might try looking
> > for
> > admin.xml or manager.xml and placing the Jetspeed.xml in the same
> > location.
> >
> > Jeremy Ford
> > [EMAIL PROTECTED]
> >
> >
> > -----Original Message-----
> > From: steve [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, March 16, 2004 12:00 PM
> > To: Jetspeed Users List
> > Subject: Re: Jetspeed2 cannot connect to datasource
> >
> > Thanks Scott. I am using Tomcat 5.0.19 (thought I read in a post that
this
> > was compatible). I will checkout this file, and if that fails, I will
try
> > your version
> > of Tomcat.
> >
> > Thanks again - I will let you know how it goes.
> >
> > Steve B.
> >
> > ----- Original Message -----
> > From: "Weaver, Scott" <[EMAIL PROTECTED]>
> > To: "'Jetspeed Users List'" <[EMAIL PROTECTED]>
> > Sent: Tuesday, March 16, 2004 12:56 PM
> > Subject: RE: Jetspeed2 cannot connect to datasource
> >
> >
> > > Hi Steve,
> > >
> > > What version of Tomcat are you running in? There is a jetspeed.xml
that
> > > should be in the webapps directory that defines the JNDI datasource in
> > > Tomcat for jetspeed. This works for me in tomcat 4.1.29.
> > >
> > > Regards,
> > > *================================*
> > > | Scott T Weaver |
> > > | <[EMAIL PROTECTED]> |
> > > | Apache Jetspeed Portal Project |
> > > | Apache Pluto Portlet Container |
> > > *================================*
> > >
> > > > -----Original Message-----
> > > > From: steve [mailto:[EMAIL PROTECTED]
> > > > Sent: Tuesday, March 16, 2004 12:39 PM
> > > > To: Jetspeed Users List
> > > > Subject: Jetspeed2 cannot connect to datasource
> > > >
> > > > I have tried several times to get help from the list on jetspeed2 to
> > no
> > > > avail. I hope my latest question is short enough that someone will
> > help.
> > > >
> > > > I have followed all the steps in the GETTING-STARTED.html without a
> > hitch
> > > > (Other than log4j not being defined). I am now calling
> > > > http://localhost:8080/jetspeed/ and am only getting a blank screen.
> > > > catalina.out seems to indicate the hsqldb datasource was not
> > configured
> > in
> > > > the installed app based on the stack trace excerpt below. Note that
I
> > do
> > > > have 'maven start.production.server' running in a seperate window.
> > > >
> > > > Could some kind soul tell me if I missed some undocumented step, or
> > simply
> > > > in what file(s) of the webapp the database connection info should be
> > > > defined? I do not get this error running maven db.recreate nor the
> > > > allBuild.
> > > >
> > > > TIA,
> > > >
> > > > Steve B.
> > > >
> > > > [org.apache.ojb.broker.accesslayer.ConnectionFactoryAbstractImpl]
> > ERROR:
> > > > SQLExce
> > > > ption thrown while trying to get Connection from Datasource
> > > > (java:comp/env/jdbc/
> > > > jetspeed)
> > > > Cannot create JDBC driver of class '' for connect URL 'null'
> > > > org.apache.commons.dbcp.SQLNestedException: Cannot create JDBC
driver
> > of
> > > > class '
> > > > ' for connect URL 'null', cause:
> > > > java.sql.SQLException: No suitable driver
> > > > at java.sql.DriverManager.getDriver(DriverManager.java:243)
> > > > at
> > > >
org.apache.commons.dbcp.BasicDataSource.createDataSource(BasicDataSou
> > > > rce.java:743)
> > > > at
> > > >
org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource
> > > > .java:518)
> > > > at
> > > >
org.apache.ojb.broker.accesslayer.ConnectionFactoryAbstractImpl.newCo
> > > > nnectionFromDataSource(Unknown Source)
> > > >
> > > >
> > > >
> > >
> ---------------------------------------------------------------------
> > > > 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]
>
> ---------------------------------------------------------------------
> 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]
