portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Le Strat <dlest...@yahoo.com>
Subject Jetspeed-2 Build Problems - Workaround
Date Mon, 17 Nov 2003 20:53:39 GMT

There seem to be a problem with Jetspeed 2 build. When
HW_App gets deployed it uses the
PortletApplicationManager in order to persist the
portlet configuration to the database.  However, given
that you have a build.properties under ${user.home}
(in Windows, it typically is C:\Documents and
Settings\Your Name), it will look for a alternate
dbAlias. If the db alias is not available, which most
likely will not, the portlets information will get
persisted to the default location,

When starting Jetspeed after the build process, you

Capability Valve Invoked
*** Getting portlet from registry: LoginPortlet
Failed to load: LoginPortlet from registry

The database used by the deployed Jetspeed is
configured in
and point to jdbc:hsqldb:/WEB-INF/db/hsql/Registry

The registry information for the deployed portlets is
then not available.

Quick workaround:

1. Copy the latest

2. Change the database reference in

Those are quick fixes, we may want to think about a
permanent way to correct this.


David Le Strat.

Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message