You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by David Le Strat <dl...@yahoo.com> on 2003/11/17 21:53:39 UTC
Jetspeed-2 Build Problems - Workaround
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: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Jetspeed-2 Build Problems - Workaround
Posted by David Le Strat <dl...@yahoo.com>.
Woops, I missed that. Thanks for pointing it out. I
agree with the point Scott made though it is not
really critical at this point.
Torque works out well for generating the database
schema.
Regards,
David.
--- David Sean Taylor <da...@bluesunrise.com> wrote:
>
> On Monday, November 17, 2003, at 08:53 PM, David Le
> Strat wrote:
>
> > 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
> >
> Look at the GETTING-STARTED.doc, step 2,
> "build.properties settings"
> See the documentation for setting the 3rd property:
> deployment.db.alias
>
> I agree that this solution is not optimal and leads
> to installation
> failures.
> The whole point of putting the database into the web
> application was to
> make Jetspeed easier to use out of the box.
> Since this is obviously not happening, perhaps we
> should drop a
> preconfigured Hypersonic database in the webapp, and
> require special
> installation steps to formally install and configure
> the database.
>
>
>
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jetspeed-dev-help@jakarta.apache.org
>
__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
Re: Jetspeed-2 Build Problems - Workaround
Posted by David Sean Taylor <da...@bluesunrise.com>.
On Monday, November 17, 2003, at 08:53 PM, David Le Strat wrote:
> 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
>
Look at the GETTING-STARTED.doc, step 2, "build.properties settings"
See the documentation for setting the 3rd property: deployment.db.alias
I agree that this solution is not optimal and leads to installation
failures.
The whole point of putting the database into the web application was to
make Jetspeed easier to use out of the box.
Since this is obviously not happening, perhaps we should drop a
preconfigured Hypersonic database in the webapp, and require special
installation steps to formally install and configure the database.
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org