From helpdesk at hippo.nl Tue Jul 1 14:41:04 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Tue Jul 1 14:41:04 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-71) check maven remote repository configuration in getting started docs Message-ID: <28988610.1214916064562.JavaMail.root@hat01> check maven remote repository configuration in getting started docs ------------------------------------------------------------------- Key: PORTAL-71 URL: http://issues.hippo.nl/browse/PORTAL-71 Project: Hippo Portal Issue Type: Bug Components: hippo-portal-docs Affects Versions: 1.07.00 Reporter: Dennis Dam Assignee: Dennis Dam Priority: Low Fix For: 1.07.00 Reported by Nick Stolwijk. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at hippo.nl Wed Jul 2 14:15:05 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Jul 2 14:15:05 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-48) Transform sitemap document with an XSLT before parsing In-Reply-To: <15969736.1203455388146.JavaMail.jira@hat01> Message-ID: <9465468.1215000905076.JavaMail.root@hat01> [ http://issues.hippo.nl/browse/PORTAL-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam reopened PORTAL-48: ------------------------------ rename XSLTTransformerService(Impl) classes to XSLTTransformer(Impl) to prevent name clashes between hippo-portal and hippo-portal-pac projects. In the future, we need a "common" project for components which are shared between different hippo-portal projects > Transform sitemap document with an XSLT before parsing > ------------------------------------------------------ > > Key: PORTAL-48 > URL: http://issues.hippo.nl/browse/PORTAL-48 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.00 > > > there is a usecase where sitemap "like" document has to be transformed to a proper sitemap format. An XSLT transformation seems to be the proper way to achieve this. The location of the XSLT file can be configured through a Source uri (via a Spring property), which can be resolved by the source resolver. In this way, the xslt can be placed on any location, e.g. a Hippo Repository, file system, JAR, etc -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From helpdesk at hippo.nl Wed Jul 9 09:41:04 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Wed Jul 9 09:41:05 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-65) create new maven-2 build configuration using jetspeed-2.2 als base portal In-Reply-To: <18968968.1212752210445.JavaMail.root@hat01> Message-ID: <30015279.1215589264643.JavaMail.root@hat01> [ http://issues.hippo.nl/browse/PORTAL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma reassigned PORTAL-65: ------------------------------- Assignee: Ate Douma (was: Dennis Dam) > create new maven-2 build configuration using jetspeed-2.2 als base portal > ------------------------------------------------------------------------- > > Key: PORTAL-65 > URL: http://issues.hippo.nl/browse/PORTAL-65 > Project: Hippo Portal > Issue Type: Sub-task > Affects Versions: 1.10.00m01 > Reporter: Ate Douma > Assignee: Ate Douma > Fix For: 1.10.00m01 > > Original Estimate: 2 days > Remaining Estimate: 2 days > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira From willem at wwwilpower.nl Wed Jul 23 11:40:03 2008 From: willem at wwwilpower.nl (Willem Vermeer) Date: Wed Jul 23 11:40:08 2008 Subject: [Hippoportal-dev] trying to run the hello-world application ... In-Reply-To: <5D95649ACDBAEB4C92E4868D1BA673F0B87F83@BA12-0008.work.local> References: <5D95649ACDBAEB4C92E4868D1BA673F0B87F83@BA12-0008.work.local> Message-ID: <18607161.post@talk.nabble.com> Hello, I'm suffering the exact same problem. I tried the suggested fix in the hosts file (adding 127.0.0.1 preview.localhost) but to no avail. Whenever I open the url http://preview.localhost:8080/gettingstarted/ the portal redirects to http://preview.localhost:8080/gettingstarted/portal and displays a HTTP Status 404 - no page matched / request in site view. I saw in my \webapps\hippo-portal\logs\hippo-portal.log the following error: ERROR nl.hippo.portal.cms.CMSSiteImpl - Failed to retrieve SiteMap document: /content/documents/construction/sitemap.xml with name: default for site: site I checked and the (up and running) Hippo repository contained a file called sitemap-xml.xml with an empty html template. So then I replaced in \conf\hippo-portal.xml at the end of the file in the entry of the property siteMapPaths by /content/documents/construction/sitemap-xml.xml but still didn't work. What am I missing? Thanks, Willem -- View this message in context: http://www.nabble.com/trying-to-run-the-hello-world-application-...-tp17015427p18607161.html Sent from the Hippo Portal development public mailinglist mailing list archive at Nabble.com. From willem at wwwilpower.nl Thu Jul 24 13:38:27 2008 From: willem at wwwilpower.nl (Willem Vermeer) Date: Thu Jul 24 13:38:42 2008 Subject: [Hippoportal-dev] trying to run the hello-world application ... In-Reply-To: <18607161.post@talk.nabble.com> References: <5D95649ACDBAEB4C92E4868D1BA673F0B87F83@BA12-0008.work.local> <18607161.post@talk.nabble.com> Message-ID: <18630135.post@talk.nabble.com> After a few more hours struggling I found out what was wrong: I didn't have a sitemap.xml in the Hippo repository and my default-layout.vm was empty. I wrote up my experiences on my blog: http://www.wwwilpower.nl/2008/07/getting-hippo-portal-up-and-running.html The current Getting Started: Hello World does not contain enough information to get a first hippo portal up and running. Willem -- View this message in context: http://www.nabble.com/trying-to-run-the-hello-world-application-...-tp17015427p18630135.html Sent from the Hippo Portal development public mailinglist mailing list archive at Nabble.com. From schans at onehippo.com Thu Jul 24 13:43:02 2008 From: schans at onehippo.com (Bart van der Schans) Date: Thu Jul 24 13:43:04 2008 Subject: [Hippoportal-dev] trying to run the hello-world application ... In-Reply-To: <18630135.post@talk.nabble.com> References: <5D95649ACDBAEB4C92E4868D1BA673F0B87F83@BA12-0008.work.local><18607161.post@talk.nabble.com> <18630135.post@talk.nabble.com> Message-ID: <48886AC6.8070901@onehippo.com> Hi Willen, Great to hear you have it up-and-running! Some of the main developers of the Hippo Portal are currently on vacation. Hence the lack of prompt feedback. I'll ask them to update the wiki with your input when they are back. Thanks for your feedback! Regards, Bart Willem Vermeer wrote: > > After a few more hours struggling I found out what was wrong: I didn't > have a > sitemap.xml in the Hippo repository and my default-layout.vm was empty. > I wrote up my experiences on my blog: > http://www.wwwilpower.nl/2008/07/getting-hippo-portal-up-and-running.html > The current Getting Started: Hello World does not contain enough information > to get a first hippo portal up and running. > Willem > > -- > View this message in context: > http://www.nabble.com/trying-to-run-the-hello-world-application-...-tp17015427p18630135.html > Sent from the Hippo Portal development public mailinglist mailing list > archive at Nabble.com. > > _______________________________________________ > Hippoportal-dev mailing list > Hippoportal-dev@lists.hippo.nl > http://lists.hippo.nl/mailman/listinfo/hippoportal-dev > -- Hippo B.V. - Amsterdam Oosteinde 11, 1017 WT, Amsterdam, +31(0)20-5224466 Hippo USA Inc. - San Francisco 101 H Street, Suite Q, Petaluma CA, 94952-3329, +1 (707) 773-4646 ----------------------------------------------------------------- http://www.onehippo.com - info@onehippo.com ----------------------------------------------------------------- From willem at wwwilpower.nl Mon Jul 28 09:55:10 2008 From: willem at wwwilpower.nl (Willem Vermeer) Date: Mon Jul 28 09:55:22 2008 Subject: [Hippoportal-dev] Error deploying second portlet app Message-ID: <18685707.post@talk.nabble.com> Hi, I got the Hippo Portal up and running with one HelloWorld portlet in it but when I try to add a second portlet application (called webshop-pa) with one very simple portlet in it, it fails during first startup. I created the second portlet app based on the hippo/maven plugin doing a maven hp:create-pa-project and maven hp:update-pa-dependencies. After startup I found the following stacktrace in the file pa.log in \webapps\webshop-pa\logs: 2008-07-28 07:58:29,987 [main] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webshop-pa] - Exception sending context initialized event to listener instance of class org.springframework.web.util.Log4jConfigListener java.lang.IllegalStateException: Web app root system property already set to different value: 'pa.root' = [c:\dev\apache-tomcat-5.5.23\webapps\hello-world-pa\] instead of [c:\dev\apache-tomcat-5.5.23\webapps\webshop-pa\] - Choose unique values for the 'webAppRootKey' context-param in your web.xml files! So there seems to be a problem with the variable webAppRootKey and its value pa.root. I tried removing this entry from my webshop-pa web.xml but then other errors start appearing. What is the goal of this parameter and what value should I assign to it when deploying more than 1 portlet app? Thanks, Willem -- View this message in context: http://www.nabble.com/Error-deploying-second-portlet-app-tp18685707p18685707.html Sent from the Hippo Portal development public mailinglist mailing list archive at Nabble.com. From j.hoffman at onehippo.com Mon Jul 28 14:07:47 2008 From: j.hoffman at onehippo.com (Jeroen Hoffman) Date: Mon Jul 28 14:07:48 2008 Subject: [Hippoportal-dev] Error deploying second portlet app References: <18685707.post@talk.nabble.com> Message-ID: Hi, I think this is a Tomcat setting, not a Hippo Portal one. Nevertheless, when running more than one app on Tomcat, all webAppRootKey init-param should be unique. Subsequently, each web app root (directory) can be retrieved from Java code using System.getProperty(key), with the configured webAppRootKey as key. If you're not using it you can leave it out. Any errors you see then have probably not to do with this. Jeroen Hoffman ________________________________ Van: hippoportal-dev-bounces@lists.hippo.nl namens Willem Vermeer Verzonden: ma 28-7-2008 9:55 Aan: hippoportal-dev@lists.hippo.nl Onderwerp: [Hippoportal-dev] Error deploying second portlet app Hi, I got the Hippo Portal up and running with one HelloWorld portlet in it but when I try to add a second portlet application (called webshop-pa) with one very simple portlet in it, it fails during first startup. I created the second portlet app based on the hippo/maven plugin doing a maven hp:create-pa-project and maven hp:update-pa-dependencies. After startup I found the following stacktrace in the file pa.log in \webapps\webshop-pa\logs: 2008-07-28 07:58:29,987 [main] ERROR org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webshop-pa] - Exception sending context initialized event to listener instance of class org.springframework.web.util.Log4jConfigListener java.lang.IllegalStateException: Web app root system property already set to different value: 'pa.root' = [c:\dev\apache-tomcat-5.5.23\webapps\hello-world-pa\] instead of [c:\dev\apache-tomcat-5.5.23\webapps\webshop-pa\] - Choose unique values for the 'webAppRootKey' context-param in your web.xml files! So there seems to be a problem with the variable webAppRootKey and its value pa.root. I tried removing this entry from my webshop-pa web.xml but then other errors start appearing. What is the goal of this parameter and what value should I assign to it when deploying more than 1 portlet app? Thanks, Willem -- View this message in context: http://www.nabble.com/Error-deploying-second-portlet-app-tp18685707p18685707.html Sent from the Hippo Portal development public mailinglist mailing list archive at Nabble.com. _______________________________________________ Hippoportal-dev mailing list Hippoportal-dev@lists.hippo.nl http://lists.hippo.nl/mailman/listinfo/hippoportal-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 5469 bytes Desc: not available Url : http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080728/81ab1c20/attachment.bin From willem at wwwilpower.nl Mon Jul 28 15:14:04 2008 From: willem at wwwilpower.nl (willem@wwwilpower.nl) Date: Mon Jul 28 15:14:06 2008 Subject: [Hippoportal-dev] Error deploying second portlet app In-Reply-To: References: <18685707.post@talk.nabble.com> Message-ID: <1217250844.488dc61cde9f1@webmail.eatserver.nl> Jeroen, Well, I tried leaving out the context-param webAppRootKey but then it didn't start up either. Finally I've replaced the value pa.root by the physical path to my deployed portlet app (c:/dev/apache-tomcat-5.5.23/webapps/webshop-pa/) and the problem went away. However, a new problem arose because now Spring complains that my webshop portlet app in its applicationContext.xml contains a duplicate applicationName (site1-pa). I replaced this applicationName by site1-webshop-pa and even added a new CMSApplicationImpl bean in my tomcat/conf/hippo-portal.xml for this name but this didn't work. Obviously at this point I no longer understand what I'm doing. Is it recommended or possible to deploy more than one portlet app to one and the same portal instance? What other steps do I need to take in this case? Thanks, Willem Quoting Jeroen Hoffman : > Hi, > I think this is a Tomcat setting, not a Hippo Portal one. Nevertheless, when > running more than one app on Tomcat, all webAppRootKey init-param should be > unique. > Subsequently, each web app root (directory) can be retrieved from Java code > using System.getProperty(key), with the configured webAppRootKey as key. If > you're not using it you can leave it out. Any errors you see then have > probably not to do with this. > > Jeroen Hoffman > > > > > > ________________________________ > > Van: hippoportal-dev-bounces@lists.hippo.nl namens Willem Vermeer > Verzonden: ma 28-7-2008 9:55 > Aan: hippoportal-dev@lists.hippo.nl > Onderwerp: [Hippoportal-dev] Error deploying second portlet app > > > > > Hi, > I got the Hippo Portal up and running with one HelloWorld portlet in it but > when I try to add a second portlet application (called webshop-pa) with one > very simple portlet in it, it fails during first startup. I created the > second portlet app based on the hippo/maven plugin doing a maven > hp:create-pa-project and maven hp:update-pa-dependencies. After startup I > found the following stacktrace in the file pa.log in > \webapps\webshop-pa\logs: > > 2008-07-28 07:58:29,987 [main] ERROR > org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webshop-pa] > - > Exception sending context initialized event to listener instance of class > org.springframework.web.util.Log4jConfigListener > java.lang.IllegalStateException: Web app root system property already set to > different value: 'pa.root' = > [c:\dev\apache-tomcat-5.5.23\webapps\hello-world-pa\] instead of > [c:\dev\apache-tomcat-5.5.23\webapps\webshop-pa\] - Choose unique values for > the 'webAppRootKey' context-param in your web.xml files! > > So there seems to be a problem with the variable webAppRootKey and its value > pa.root. I tried removing this entry from my webshop-pa web.xml but then > other errors start appearing. What is the goal of this parameter and what > value should I assign to it when deploying more than 1 portlet app? > > Thanks, > Willem > -- > View this message in context: > http://www.nabble.com/Error-deploying-second-portlet-app-tp18685707p18685707.html > Sent from the Hippo Portal development public mailinglist mailing list > archive at Nabble.com. > > _______________________________________________ > Hippoportal-dev mailing list > Hippoportal-dev@lists.hippo.nl > http://lists.hippo.nl/mailman/listinfo/hippoportal-dev > > > From j.hoffman at onehippo.com Tue Jul 29 10:33:03 2008 From: j.hoffman at onehippo.com (Jeroen Hoffman) Date: Tue Jul 29 10:33:05 2008 Subject: [Hippoportal-dev] Error deploying second portlet app References: <18685707.post@talk.nabble.com> <1217250844.488dc61cde9f1@webmail.eatserver.nl> Message-ID: It should be possible to deploy multiple portlet applications in Hippo Portal. The app's id/name should be the same in all occurences; in portlet.xml and applicationContext.xml in the portlet app project. In hippo-portal.xml there should be a registration configured indeed; a CMSApplicationImpl with the correct name and a reference to it in CMSApplicationRegistry. This last part registers the application to a shared object so the portal and portlet-pa can communicate, see http://portal.hippocms.org/about/architecture.html HTH Jeroen ________________________________ Van: hippoportal-dev-bounces@lists.hippo.nl namens willem@wwwilpower.nl Verzonden: ma 28-7-2008 15:14 Aan: Hippo Portal development public mailinglist Onderwerp: RE: [Hippoportal-dev] Error deploying second portlet app Jeroen, Well, I tried leaving out the context-param webAppRootKey but then it didn't start up either. Finally I've replaced the value pa.root by the physical path to my deployed portlet app (c:/dev/apache-tomcat-5.5.23/webapps/webshop-pa/) and the problem went away. However, a new problem arose because now Spring complains that my webshop portlet app in its applicationContext.xml contains a duplicate applicationName (site1-pa). I replaced this applicationName by site1-webshop-pa and even added a new CMSApplicationImpl bean in my tomcat/conf/hippo-portal.xml for this name but this didn't work. Obviously at this point I no longer understand what I'm doing. Is it recommended or possible to deploy more than one portlet app to one and the same portal instance? What other steps do I need to take in this case? Thanks, Willem Quoting Jeroen Hoffman : > Hi, > I think this is a Tomcat setting, not a Hippo Portal one. Nevertheless, when > running more than one app on Tomcat, all webAppRootKey init-param should be > unique. > Subsequently, each web app root (directory) can be retrieved from Java code > using System.getProperty(key), with the configured webAppRootKey as key. If > you're not using it you can leave it out. Any errors you see then have > probably not to do with this. > > Jeroen Hoffman > > > > > > ________________________________ > > Van: hippoportal-dev-bounces@lists.hippo.nl namens Willem Vermeer > Verzonden: ma 28-7-2008 9:55 > Aan: hippoportal-dev@lists.hippo.nl > Onderwerp: [Hippoportal-dev] Error deploying second portlet app > > > > > Hi, > I got the Hippo Portal up and running with one HelloWorld portlet in it but > when I try to add a second portlet application (called webshop-pa) with one > very simple portlet in it, it fails during first startup. I created the > second portlet app based on the hippo/maven plugin doing a maven > hp:create-pa-project and maven hp:update-pa-dependencies. After startup I > found the following stacktrace in the file pa.log in > \webapps\webshop-pa\logs: > > 2008-07-28 07:58:29,987 [main] ERROR > org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/webshop-pa] > - > Exception sending context initialized event to listener instance of class > org.springframework.web.util.Log4jConfigListener > java.lang.IllegalStateException: Web app root system property already set to > different value: 'pa.root' = > [c:\dev\apache-tomcat-5.5.23\webapps\hello-world-pa\] instead of > [c:\dev\apache-tomcat-5.5.23\webapps\webshop-pa\] - Choose unique values for > the 'webAppRootKey' context-param in your web.xml files! > > So there seems to be a problem with the variable webAppRootKey and its value > pa.root. I tried removing this entry from my webshop-pa web.xml but then > other errors start appearing. What is the goal of this parameter and what > value should I assign to it when deploying more than 1 portlet app? > > Thanks, > Willem > -- > View this message in context: > http://www.nabble.com/Error-deploying-second-portlet-app-tp18685707p18685707.html > Sent from the Hippo Portal development public mailinglist mailing list > archive at Nabble.com. > > _______________________________________________ > Hippoportal-dev mailing list > Hippoportal-dev@lists.hippo.nl > http://lists.hippo.nl/mailman/listinfo/hippoportal-dev > > > _______________________________________________ Hippoportal-dev mailing list Hippoportal-dev@lists.hippo.nl http://lists.hippo.nl/mailman/listinfo/hippoportal-dev -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 7409 bytes Desc: not available Url : http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080729/35890844/attachment.bin From helpdesk at hippo.nl Thu Jul 31 14:12:56 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Thu Jul 31 14:12:55 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-72) hp:build-portal resets the jetspeed version to 2.1.3 while a certain revision was set in build files Message-ID: <25410369.1217506376099.JavaMail.jira@hat01> hp:build-portal resets the jetspeed version to 2.1.3 while a certain revision was set in build files ---------------------------------------------------------------------------------------------------- Key: PORTAL-72 URL: http://issues.hippo.nl/browse/PORTAL-72 Project: Hippo Portal Issue Type: Bug Components: hippo-portal-maven-plugin Reporter: Jeroen Hoffman Priority: Normal In build files full-portal.xml and jetspeed-component.xml, dependencies to jetspeed were set to a certain revision of jetspeed. When building with the hippoportal maven 1 plugin, these dependencies are reset to 2.1.3, resulting in the wrong jars to be included in the war build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.hippo.nl/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira