All,
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,
${jetspeed.home}/portal/src/webapp/WEB-INF/db/hsql
When starting Jetspeed after the build process, you
get:
Capability Valve Invoked
*** Getting portlet from registry: LoginPortlet
org.apache.jetspeed.exception.JetspeedException:
Failed to load: LoginPortlet from registry
The database used by the deployed Jetspeed is
configured in
${tomcat.home}/webapps\jetspeed/WEB-INF/conf/registry-hsql-database.xml
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
${jetspeed.home}/portal/src/webapp/WEB-INF/db/hsql/Registry.script
to
${tomcat.home}/webapps\jetspeed/WEB-INF/db/hsql/Registry.script
2. Change the database reference in
${tomcat.home}/webapps\jetspeed/WEB-INF/conf/registry-hsql-database.xml
Those are quick fixes, we may want to think about a
permanent way to correct this.
Regards,
David Le Strat.
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
