From helpdesk at hippo.nl Mon Sep 1 14:16:00 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Mon Sep 1 14:16:00 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-75) Dynamic PSML resolving Message-ID: <32346797.1220271360757.JavaMail.jira@hat01> Dynamic PSML resolving ---------------------- Key: PORTAL-75 URL: http://issues.hippo.nl/browse/PORTAL-75 Project: Hippo Portal Issue Type: Improvement Components: hippo-portal-j2 Affects Versions: 1.07.00, 1.10.00m01 Reporter: Dennis Dam Assignee: Dennis Dam Priority: Normal Fix For: 1.07.00, 1.10.00m01 Currently, the resolved location of a psml is based on the type of the resolved sitemap item. This feature would add the ability to override the default location of the PSML, which could be derived from the resolved CMSRequestContext. An existing usecase is to fetch the type of the associated detail document (the type is stored as webdav property), and use that to locate the PSML. This would allow mapping detail urls under 1 sitemap item to different PSMLs. -- 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 Mon Sep 1 15:28:00 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 1 15:28:00 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-76) Request for support to add a new portlet application without having to adjust hippo-portal.xml Message-ID: <16634370.1220275680574.JavaMail.jira@hat01> Request for support to add a new portlet application without having to adjust hippo-portal.xml ---------------------------------------------------------------------------------------------- Key: PORTAL-76 URL: http://issues.hippo.nl/browse/PORTAL-76 Project: Hippo Portal Issue Type: New Feature Components: hippo-portal Reporter: Jeroen Hoffman Priority: Normal When a new portlet application is added, it has to be registered in hippo-portal.xml by means of a CMSApplicationImpl. It would be nice if a mechanism was introduced that avoids this necessity. Suggestion to configure a CMSApplicationFactory property in CMSApplicationRegistry. Or, check wether registration is actually necessary for a second pa, in case of a common user service, as that is the only usage of the registry, so it seems. -- 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 Tue Sep 2 10:08:08 2008 From: willem at wwwilpower.nl (Willem Vermeer) Date: Tue Sep 2 10:08:18 2008 Subject: [Hippoportal-dev] NullPointer when using BreadCrumbPortlet Message-ID: <19265854.post@talk.nabble.com> Hi, When using the BreadCrumbPortlet we encounter a NullPointerException in SiteNavigation line 61, when the code tries to retrieve a homeItem by: SiteMapItem homeItem = cmsRequestContext.getSiteMapItem().getSiteMap().getById("home"); this can't be found and on the next line homeItem.getTitle() throws the NPE. Could this be a problem in our repository? How exactly does getById work, is it sufficient to add an home entry in sitemenu.xml or must it be a DAV property? Stacktrace below. Thanks Willem 10:06:04,091 ERROR [STDERR] java.lang.NullPointerException 10:06:04,091 ERROR [STDERR] at nl.hippo.portal.cms.site.SiteNavigation.getBreadcrumbs(SiteNavigation.java:61) 10:06:04,091 ERROR [STDERR] at nl.hippo.portal.cms.portlets.BreadcrumbsPortlet.createFreeMarkerModel(BreadcrumbsPortlet.java:57) 10:06:04,091 ERROR [STDERR] at nl.hippo.portal.cms.portlets.FreeMarkerContentPortlet.doView(FreeMarkerContentPortlet.java:37) 10:06:04,091 ERROR [STDERR] at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:247) 10:06:04,091 ERROR [STDERR] at javax.portlet.GenericPortlet.render(GenericPortlet.java:175) 10:06:04,091 ERROR [STDERR] at nl.hippo.portal.cms.portlets.CMSContextPortlet.render(CMSContextPortlet.java:96) 10:06:04,091 ERROR [STDERR] at org.apache.jetspeed.factory.JetspeedPortletInstance.render(JetspeedPortletInstance.java:103) 10:06:04,091 ERROR [STDERR] at org.apache.jetspeed.container.JetspeedContainerServlet.doGet(JetspeedContainerServlet.java:277) 10:06:04,091 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) 10:06:04,091 ERROR [STDERR] at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) -- View this message in context: http://www.nabble.com/NullPointer-when-using-BreadCrumbPortlet-tp19265854p19265854.html Sent from the Hippo Portal development public mailinglist mailing list archive at Nabble.com. From nico.tromp at gmail.com Sat Sep 6 17:39:05 2008 From: nico.tromp at gmail.com (Nico Tromp) Date: Sat Sep 6 17:39:20 2008 Subject: [Hippoportal-dev] Re: Using FreemarkerListContenPortlet to display content from repository files In-Reply-To: <48B3B84C.4020200@onehippo.com> References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com> <48B280FA.7030908@onehippo.com> <439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com> <48B3B84C.4020200@onehippo.com> Message-ID: <439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Actually I need some fields from the XML content. I prefer the FM portlets because they look more like plain HTML. For the time being I stick to the solution we already implemented. Cheers Nico Tromp On 8/26/08, Dennis Dam wrote: > Ah ok, I see what you're trying to do now.. if you want to show the full > content of a bunch of XML files (the result of a dasl query) , I would > recommend using XSLTListContentPortlet instead of > FreeMarkerListContentPortlet. The latter one is more suitable for > showing metadata (webdav properties) of XML documents, while the first > one is very simple to use for showing the *full* content of XML > documents. See also the reply from Wessel. > > Dennis > > > Nico Tromp wrote: >> Dennis, >> >> I am actualy interested in the content from a bunch of XML files that >> reside in our repository, that's why I use a ListContentPortlet. I >> like the FreemarkerListContentPortlet because of it simplicity. If I'm >> correct the demo app uses meta-data. The meta-data can be retreived by >> using some usefull methods like getPropertyValue() or something like >> that. Getting data from the content is a whole other story. I didn't >> find any examples. >> >> At this moment we're unmarshalling the XML content into a simple Java >> object structure and are using that for showing are list with content. >> I don't like this because of the overhead it generates. I think it >> should be possible to use the XML content within the >> FreemarkerListContentPortlet. >> >> >> Kind regards >> >> Nico >> >> >> On Mon, Aug 25, 2008 at 11:52 AM, Dennis Dam > > wrote: >> >> Hi Nico, >> >> you shouldn't use FreeMarkerListContentPortlet for presenting XML >> from repository files. The word "list" in this portlet names means >> that is meant to be used for showing the results of a DASL search >> operation. The portlet that can be best used for presenting >> repository XML files is XSLTContentPortlet. An example >> configuration of this portlet is available in demo-portal [1]. Let >> me know if you have further questions. >> >> Dennis >> >> [1] >> >> https://svn.hippocms.org/repos/hippo/hippo-portal/trunk/demo-portal/src/webapp/WEB-INF/pages/__demo-site/news-detail.psml >> >> Nico Tromp wrote: >> >> Hi all, >> >> can somebody giv me a pointer on displaying content from a >> repository file using the FreemarkerListContentPortlet? >> >> I have a DASL query that returns files from the repository. I >> have a freemarker template for displaying the content from the >> repository files. I'am able to do the easy stuff like: >> >> 1: ${searchResults.size()} >> 2: <#list searchResults.iterator() as singleFile> >> 3: <#assign xmlContent = singleFile.responseAsDom> >> 4: ${xmlContent.getElementsByTagName("name").length} >> >> Lines 1 and 4 are just to ensure that my DASL query is >> returning anything at all. >> >> Once I get the 'name' element I need the value. I tried things >> like: >> >> 5: >> ${xmlContent.getElementsByTagName("name").item(0).getNodeValue() >> 6: ${xmlContent.name} >> >> But nothing seems to work. I get all kinds of exceptions. >> >> >> Kind regards >> >> Nico >> >> ------------------------------------------------------------------------ >> >> >> >> _______________________________________________ >> 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 >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Hippoportal-dev mailing list >> Hippoportal-dev@lists.hippo.nl >> http://lists.hippo.nl/mailman/listinfo/hippoportal-dev >> > > > -- > Hippo > > d.dam@onehippo.com > > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 > San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 > +1 (707) 773-4646 > > www.onehippo.com info@onehippo.com > > _______________________________________________ > Hippoportal-dev mailing list > Hippoportal-dev@lists.hippo.nl > http://lists.hippo.nl/mailman/listinfo/hippoportal-dev > From vdweij at hotmail.com Tue Sep 9 14:27:05 2008 From: vdweij at hotmail.com (=?iso-8859-1?Q?=C6de_van_der_Weij?=) Date: Tue Sep 9 14:27:09 2008 Subject: [Hippoportal-dev] Invalidate cache entry manually In-Reply-To: <439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com> <48B280FA.7030908@onehippo.com> <439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com> <48B3B84C.4020200@onehippo.com> <439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Hi all, I am facing the current issue. A portal page has a portlet A that will create a document in the repository and a portlet B that lists the content of that directory. When I create an item in portlet A and the doView of portlet B is called, the cache is not yet invalidated and portlet B will list the content of the directory without the newly created item. At first I thought is was due to a delay in indexation by Lucene, but than I found out is was because the result of a previous DASL search has not yet been invalidated. My plan is to invalidate the cache for that particular search right after I've created that new item. I can get hold of the ObjectCache through getCMSRequestContext().getSite().getObjectCache(), but after that I am not sure what to do. What I would like to know is if this strategy is feasible. If so I would like to get some pointers. If not I would like to know alternative solutions. Any help is appreciated. --?de _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080909/4d2659ec/attachment.htm From a.schrijvers at onehippo.com Tue Sep 9 14:40:30 2008 From: a.schrijvers at onehippo.com (Ard Schrijvers) Date: Tue Sep 9 14:40:32 2008 Subject: [Hippoportal-dev] Invalidate cache entry manually In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com> <439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Hello ?de, Though I am not really aware about portal things, I do know the webdav adapter caching mechanism, and why it works like it does. Also, I understand what you want to achieve. First of all let me emphasize that you can only get desired behavior *if* and only *if* you are talking about a document listing or some propfind. Anything that does a search, will not satisfy your needs, because the lucene index is not updated untill the jms event is fired. So, if you are not using a search, and you want to invalidate, you have two options: 1) try to fire a jms event yourself from the portal 2) we could add an interface to the caching of the webdav adapter such that you can 'throw' in namedEvents yourself to invalidate instantly without waiting for a jms from the repository (this is what I actually chose for in the cms, since the cms caches directory listings, but adding a new document is visible instantly, before the jms arrived. This is though build in cocoon and does not use the webdav adapter, which, currently does not have any access for invalidating items yourself) Regards ard > Hi all, > > I am facing the current issue. A portal page has a portlet A > that will create a document in the repository and a portlet B > that lists the content of that directory. When I create an > item in portlet A and the doView of portlet B is called, the > cache is not yet invalidated and portlet B will list the > content of the directory without the newly created item. > > At first I thought is was due to a delay in indexation by > Lucene, but than I found out is was because the result of a > previous DASL search has not yet been invalidated. > > My plan is to invalidate the cache for that particular search > right after I've created that new item. I can get hold of the > ObjectCache through > getCMSRequestContext().getSite().getObjectCache(), but after > that I am not sure what to do. > > What I would like to know is if this strategy is feasible. If > so I would like to get some pointers. If not I would like to > know alternative solutions. > > Any help is appreciated. > > --?de > > > ________________________________ > > Express yourself instantly with MSN Messenger! MSN Messenger > > From vdweij at hotmail.com Tue Sep 9 14:56:11 2008 From: vdweij at hotmail.com (=?iso-8859-1?Q?=C6de_van_der_Weij?=) Date: Tue Sep 9 14:56:25 2008 Subject: [Hippoportal-dev] Invalidate cache entry manually In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com> <439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Ard, > So, if you are not using a search, and you want to invalidate, you have two options: We are using a search :) > 1) try to fire a jms event yourself from the portal > 2) we could add an interface to the caching of the webdav adapter such that you can 'throw' in namedEvents yourself to invalidate instantly without waiting for a jms from the repository (this is what I actually chose for in the cms, since the cms caches directory listings, but adding a new document is visible instantly, before the jms arrived. This is though build in cocoon and does not use the webdav adapter, which, currently does not have any access for invalidating items yourself) I like option 2 because of it's instantaneously character. Further more option 1 does not guarantee that the event is fired before the portlet is rendered. Could you please elaborate on option 2. Or point to an example. --?de _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080909/e9babad2/attachment.htm From a.schrijvers at onehippo.com Tue Sep 9 15:04:17 2008 From: a.schrijvers at onehippo.com (Ard Schrijvers) Date: Tue Sep 9 15:04:18 2008 Subject: [Hippoportal-dev] Invalidate cache entry manually In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Hello ?de, > Ard, > > > > So, if you are not using a search, and you want to > invalidate, you have two options: > > We are using a search :) Well....then you won't gain anything, because the lucene index won't be updated yet, hence returning you the same result you already had in cache. You can configure in the repository after how many seconds the indexing queue is processed (it's a cron job, something like 0/5 0 0 0 , you can find it). If you set it to 0/1 (1 sec), you would have most likely a jms event within one second. Perhaps you can have some delay for the second portal or is this out of the question? > > > 1) try to fire a jms event yourself from the portal > > 2) we could add an interface to the caching of the webdav > adapter such > > that you can 'throw' in namedEvents yourself to invalidate > instantly > > without waiting for a jms from the repository (this is what > I actually > > chose for in the cms, since the cms caches directory listings, but > > adding a new document is visible instantly, before the jms arrived. > > This is though build in cocoon and does not use the webdav adapter, > > which, currently does not have any access for invalidating items > > yourself) > > I like option 2 because of it's instantaneously character. > Further more option 1 does not guarantee that the event is > fired before the portlet is rendered. > > Could you please elaborate on option 2. Or point to an example. >From the top of my head I really can't. First of all, I do not know how the portal encorporates the webdav adapter, and secondly, I would have to invest *how* to supply this feature from the webdav adapter pov. And, as elaborated above, I doubt whether this results in your requested behavior. Recapitulating, I would really need to invest time to sort it out for you. -Ard > > --?de > > > > ________________________________ > > Express yourself instantly with MSN Messenger! MSN Messenger > > From vdweij at hotmail.com Tue Sep 9 15:22:44 2008 From: vdweij at hotmail.com (=?iso-8859-1?Q?=C6de_van_der_Weij?=) Date: Tue Sep 9 15:22:47 2008 Subject: [Hippoportal-dev] Invalidate cache entry manually In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Ard, > > > So, if you are not using a search, and you want to > > invalidate, you have two options: > > > > We are using a search :) > > Well....then you won't gain anything, because the lucene index won't be updated yet, hence returning you the same result you already had in cache. You can configure in the repository after how many seconds the indexing queue is processed (it's a cron job, something like 0/5 0 0 0 , you can find it). If you set it to 0/1 (1 sec), you would have most likely a jms event within one second. Perhaps you can have some delay for the second portal or is this out of the question? Ok, I'll try to play with the settings and also I'll try to replace the search for a directory listing. > > I like option 2 because of it's instantaneously character. > > Further more option 1 does not guarantee that the event is > > fired before the portlet is rendered. > > > > Could you please elaborate on option 2. Or point to an example. > > >From the top of my head I really can't. First of all, I do not know how the portal encorporates the webdav adapter, and secondly, I would have to invest *how* to supply this feature from the webdav adapter pov. And, as elaborated above, I doubt whether this results in your requested behavior. Recapitulating, I would really need to invest time to sort it out for you. I see. For now leave this issue as is, but I most likely get back on it. Thanks so far. --?de _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080909/d452d788/attachment.htm From a.schrijvers at onehippo.com Tue Sep 9 15:31:01 2008 From: a.schrijvers at onehippo.com (Ard Schrijvers) Date: Tue Sep 9 15:31:02 2008 Subject: [Hippoportal-dev] Invalidate cache entry manually In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: > > Ard, > > > > > So, if you are not using a search, and you want to > > > invalidate, you have two options: > > > > > > We are using a search :) > > > > Well....then you won't gain anything, because the lucene > index won't be updated yet, hence returning you the same > result you already had in cache. You can configure in the > repository after how many seconds the indexing queue is > processed (it's a cron job, something like 0/5 0 0 0 , you > can find it). If you set it to 0/1 (1 sec), you would have > most likely a jms event within one second. Perhaps you can > have some delay for the second portal or is this out of the question? > > Ok, I'll try to play with the settings and also I'll try to > replace the search for a directory listing. Other people have used it like this before: Set the indexing settings to 1 sec, and wait for the jms... There was a moment I wanted to add behavior for this in the repository to be able to block a request (when configured so) untill indexing was finished (such that you would never get a result that did not have the latest changes). However, our new repository 2 has all these functionalities in it, and many more, so I'd rather focus on making the new one better. Hope you agree :-) -Ard > > > > I like option 2 because of it's instantaneously character. > > > Further more option 1 does not guarantee that the event is fired > > > before the portlet is rendered. > > > From vdweij at hotmail.com Tue Sep 9 15:36:48 2008 From: vdweij at hotmail.com (=?iso-8859-1?Q?=C6de_van_der_Weij?=) Date: Tue Sep 9 15:36:58 2008 Subject: [Hippoportal-dev] Use PortletResourceURLFactory to render csv file In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Hi all, The PortletResourceURLFactory was mentioned to me in another post for AJAX purposes but I think I could also use it to render a csv file. A portal page has a portlet that display search results. Now the idea is that a user should be able to download this result in csv format. I only found some wicked examples concerning the use of PortletResourceURLFactory whereas I'm actually looking for an example on how to combine it with a ListContentPortlet (or some other Hippo based portlet). Any help is appriciated --?de _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080909/e0a69dae/attachment.htm From willem at wwwilpower.nl Tue Sep 9 15:56:13 2008 From: willem at wwwilpower.nl (willem@wwwilpower.nl) Date: Tue Sep 9 15:56:21 2008 Subject: [Hippoportal-dev] Use PortletResourceURLFactory to render csv file In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: <1220968573.48c6807d3b196@webmail.eatserver.nl> Hi ?de, Maybe I can help you, we've recently implemented resourceURLs for Ajax requests. It's a JSR286 feature already available in the current Hippo portal. First you have to create a resourceURL factory : org.apache.portals.bridges.common.PortletResourceURLFactory resourceURLFactory = new org.apache.jetspeed.portlet.PortletResourceURLFactoryImpl(); I've put this code in the init(config) method of a portlet and store this factory in a private instance variable. Now in your portlet render template you must use an URL generated by this factory. We prepare this URL in the portlet code and store it in the Freemarker model: model.put("ajaxurl", resourceURLFactory.createResourceURL(getPortletConfig(), request, response, null)); Refer to this url in your form:
..
Now, when this form gets submitted, you will receive a hit on your doView method and you can inspect the request to check whether it was a resource request or a normal request: org.apache.jetspeed.request.RequestContext jrc = (org.apache.jetspeed.request.RequestContext) request.getAttribute(org.apache.jetspeed.PortalReservedParameters.REQUEST_CONTEXT_ATTRIBUTE); if (jrc.getPortalURL().getNavigationalState().getPortletWindowOfResource()!=null) { // it was a resource request } else { // it was a normal render request } Now you have full control over the response and can set its content type and get the output stream to pass back whatever content you like without going through the portal aggregating cycle. (This solution was based on input we received from Hippo experts) HTH, Willem Citeren ?de van der Weij : > Hi all, > > The PortletResourceURLFactory was mentioned to me in another post for AJAX > purposes but I think I could also use it to render a csv file. A portal page > has a portlet that display search results. Now the idea is that a user should > be able to download this result in csv format. > > I only found some wicked examples concerning the use of > PortletResourceURLFactory whereas I'm actually looking for an example on how > to combine it with a ListContentPortlet (or some other Hippo based portlet). > > Any help is appriciated > > --?de > > _________________________________________________________________ > Express yourself instantly with MSN Messenger! Download today it's FREE! > http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ From a.douma at onehippo.com Tue Sep 9 16:08:52 2008 From: a.douma at onehippo.com (Ate Douma) Date: Tue Sep 9 16:13:03 2008 Subject: [Hippoportal-dev] Use PortletResourceURLFactory to render csv file References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Hi ?de, Indeed Jetspeed-2 has a "pre-JSR-286" PortletResourceURLFactory solution which is very similar to (and actually based upon) the new Portlet API 2.0 PortletResourceURL feature. When a PortletResourceURL is invoked only the target portlet itself will be executed for which it will have full control over the response. Thus this feature can be used for handling Ajax calls or something like dynamic image generation (by the portlet itself). As within Jetspeed this still is a pre JSR-286 solution, it is technically implemented as a customized RenderURL. This means that *handling* such a request needs to be done in the Portlet render method (or more commonly: GenericPortlet.doView). To create a PortletResourceURL the Portlet first needs to create an instance of the PortletResourceURLFactory, for example like this: MyPortlet.java import org.apache.portals.bridges.common.PortletResourceURLFactory; private PorletResourceURLFactory resourceURLFactory; public void init(PortletConfig config) throws PortletException { super.init(config); ... try { Class clazz = Class.forName("org.apache.jetspeed.portlet.PortletResourceURLFactoryImpl"); resourceURLFactory = (PortletResourceURLFactory)clazz.newInstance(); } catch (Exception e) { throw new PortletException("Initialization failure", e); } } Then, creating a ResourceURL use the retrieved factory as follows: String url = resourceURLFactory.createResourceURL(PortletConfig, RenderRequest, RenderResponse, Map parameters); See also: http://portals.apache.org/bridges/multiproject/portals-bridges-common/xref/org/apache/portals/bridges/common/PortletResourceURLFactory.html Finally, recognizing an incoming ResourceURL request in the doView method currently requires a little clunky solution... While adding this feature to Jetspeed I forgot to provide a predefined marker like an attribute which could be checked. This will be added in a future release, but for now you need to useeither: a) add a custom predefined (and reserved) parameter on the resourceURL and check for it in the doView, e.g. something like: public static String PORTLET_RESOURCE_URL_MARKER = "_ru"; String createResourceURL(RenderRequest req, RenderResponse res, Map parameters) { parameters.add(PORTLET_RESOURCE_URL_MARKER,"true"); return resourceURLFactory.createResourceURL(getPortletConfig(), req, res, parameters); } then, in the doView: protected void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException { if (request.getParameter(PORTLET_RESOURCE_URL_MARKER) != null) { // ResourceRequest } else { // renderRequest } } or: b) use the internal Jetspeed API to explicitely detect it (as Jetspeed itself does) protected void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException { JetspeedRequestContext jrc = (JetspeedRequestContext)request.getAttribute(PortalReservedParameters.REQUEST_CONTEXT_ATTRIBUTE); if (jrc.getPortalURL().getNavigationalState().getPortletWindowOfResource() != null) { // ResourceRequest } else { // renderRequest } } HTH, Ate -- a.douma@onehippo.com www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1(877) 41-HIPPO -----Original Message----- From: hippoportal-dev-bounces@lists.hippo.nl on behalf of ?de van der Weij Sent: Tue 9/9/2008 3:36 PM To: Hippo Portal development public mailinglist Subject: [Hippoportal-dev] Use PortletResourceURLFactory to render csv file Hi all, The PortletResourceURLFactory was mentioned to me in another post for AJAX purposes but I think I could also use it to render a csv file. A portal page has a portlet that display search results. Now the idea is that a user should be able to download this result in csv format. I only found some wicked examples concerning the use of PortletResourceURLFactory whereas I'm actually looking for an example on how to combine it with a ListContentPortlet (or some other Hippo based portlet). Any help is appriciated --?de ________________________________ Express yourself instantly with MSN Messenger! MSN Messenger -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/ms-tnef Size: 5583 bytes Desc: not available Url : http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080909/313e638d/attachment.bin From vdweij at hotmail.com Wed Sep 10 11:39:37 2008 From: vdweij at hotmail.com (=?iso-8859-1?Q?=C6de_van_der_Weij?=) Date: Wed Sep 10 11:39:47 2008 Subject: [Hippoportal-dev] Use PortletResourceURLFactory to render csv file In-Reply-To: <1220968573.48c6807d3b196@webmail.eatserver.nl> References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> <1220968573.48c6807d3b196@webmail.eatserver.nl> Message-ID: Willem, It works beautifully! Thanks. Virtually the same as Ate described in his answer :) --?de _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080910/935e4ca9/attachment.htm From vdweij at hotmail.com Wed Sep 10 11:40:19 2008 From: vdweij at hotmail.com (=?iso-8859-1?Q?=C6de_van_der_Weij?=) Date: Wed Sep 10 11:40:25 2008 Subject: [Hippoportal-dev] Use PortletResourceURLFactory to render csv file In-Reply-To: References: <439bd37e0808201238y34742b06yec82042492686486@mail.gmail.com><48B280FA.7030908@onehippo.com><439bd37e0808250703i4d077dc9he0fec105d8f6907e@mail.gmail.com><48B3B84C.4020200@onehippo.com><439bd37e0809060839j410527f1v6cd3c90e08438427@mail.gmail.com> Message-ID: Ate, It works beautifully! Thanks. Virtually the same as Willem described in his answer :) And this answer his also similar ;) --?de _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080910/16231b2a/attachment.htm From dtaylor at onehippo.com Mon Sep 15 16:44:08 2008 From: dtaylor at onehippo.com (David Sean Taylor) Date: Mon Sep 15 16:44:16 2008 Subject: [Hippoportal-dev] Re: Profiling with roles In-Reply-To: References: Message-ID: <8FEDBED5-4CC2-4146-ABD0-0C39930336DF@onehippo.com> Hi Jeroen, Sounds like you completed steps 1,2, now for steps 3,4: 3. assign the role "mavb-organization" to your user(s). The profiler only aggregates role pages based on the profile of the user, i.e. which roles the user has 4. assign the role-fallback rule to each user who you want to use the role-fallback. you can make also make the role-fallback rule the default rule, or via the user admin, when you create new users, have profiling rules (and roles) auto assigned based on the User Admin portlet instance preferences (you can have more than one User Admin portlets with different prefs) see the FAQ here: http://portals.apache.org/jetspeed-2/faq.html Finally, if you are importing users, the XML seed data can be used to define the profiling rule and roles of a user dtaylor@onehippo.com www.onehippo.com San Francisco - Hippo USA Inc. 101 H Street, Suite Q Petaluma CA 94952-3329 +1 (877) 41-HIPPO Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 On Sep 15, 2008, at 5:34 AM, Jeroen Hoffman wrote: > Hi David, > I have a question on how to implement a role based profiling. I'm > trying to present a diferent home page for different roles, which > Ate tells me is supported out-of-the-box by Jetspeed. So I did the > following: > - I added a j2 role 'mavb-organization' to a particular user in the > used LDAP > - I created a directory pages/_role/mavb-organization and placed > files home.psml and folder.metadata in it, setting the page> in folder.metadata to home.psml > > Now, based on a simple URL ending with /portal, I'd expect the > profiler to look at directory pages/_role/mavb-organization for psml > files, but it doesn't. The URL /portal/home.psml also does not lead > to show the role specific page. > > I've looked at the profiler code and debugged, trying to understand > it and get it working, but didn't succeed so far. > The RoleCriterionResolver isn't even called, nor is > RoleFallbackProfilingRule. What am I missing here, a wrong URL, or > should I add/change rules or criteria in the database? > > Thanks > Jeroen > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080915/81662ab8/attachment.htm From willem at wwwilpower.nl Tue Sep 16 09:14:37 2008 From: willem at wwwilpower.nl (Willem Vermeer) Date: Tue Sep 16 09:14:43 2008 Subject: [Hippoportal-dev] NullPointer when using BreadCrumbPortlet In-Reply-To: <19265854.post@talk.nabble.com> References: <19265854.post@talk.nabble.com> Message-ID: <19506576.post@talk.nabble.com> Can anybody help me on this one? Thanks, Willem -- View this message in context: http://www.nabble.com/NullPointer-when-using-BreadCrumbPortlet-tp19265854p19506576.html Sent from the Hippo Portal development public mailinglist mailing list archive at Nabble.com. From d.dam at onehippo.com Tue Sep 16 10:01:24 2008 From: d.dam at onehippo.com (Dennis Dam) Date: Tue Sep 16 10:01:25 2008 Subject: [Hippoportal-dev] NullPointer when using BreadCrumbPortlet In-Reply-To: <19506576.post@talk.nabble.com> References: <19265854.post@talk.nabble.com> <19506576.post@talk.nabble.com> Message-ID: <48CF67D4.6010006@onehippo.com> Sorry Willem, it seems like I totally overlooked your question. To answer your question, the line cmsRequestContext.getSiteMapItem().getSiteMap().getById("home"); will look up an "item" with id "home" in sitemap.xml. So the value "home" is not in a property, but is the value of the ID element of a "fixed-item" or (exclusive) menu-item fetched in the sitemap document. hth, Dennis Willem Vermeer wrote: > Can anybody help me on this one? > Thanks, > Willem > > From j.hoffman at onehippo.com Tue Sep 16 11:05:26 2008 From: j.hoffman at onehippo.com (Jeroen Hoffman) Date: Tue Sep 16 11:05:28 2008 Subject: [Hippoportal-dev] Re: Profiling with roles In-Reply-To: <8FEDBED5-4CC2-4146-ABD0-0C39930336DF@onehippo.com> References: <8FEDBED5-4CC2-4146-ABD0-0C39930336DF@onehippo.com> Message-ID: <48CF76D6.9090302@onehippo.com> I had my security constraints in the psml wrong as well, but now I got it working allright! Thanks Jeroen David Sean Taylor wrote: > Hi Jeroen, > > Sounds like you completed steps 1,2, now for steps 3,4: > > 3. assign the role "mavb-organization" to your user(s). The profiler > only aggregates role pages based on the profile of the user, i.e. which > roles the user has > 4. assign the role-fallback rule to each user who you want to use the > role-fallback. you can make also make the role-fallback rule the default > rule, or via the user admin, when you create new users, have profiling > rules (and roles) auto assigned based on the User Admin portlet instance > preferences (you can have more than one User Admin portlets with > different prefs) see the FAQ here: > > http://portals.apache.org/jetspeed-2/faq.html > > Finally, if you are importing users, the XML seed data can be used to > define the profiling rule and roles of a user > > dtaylor@onehippo.com www.onehippo.com > > San Francisco - Hippo USA Inc. 101 H Street, Suite Q Petaluma CA > 94952-3329 +1 (877) 41-HIPPO > Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 > > > > On Sep 15, 2008, at 5:34 AM, Jeroen Hoffman wrote: > >> Hi David, >> I have a question on how to implement a role based profiling. I'm >> trying to present a diferent home page for different roles, which Ate >> tells me is supported out-of-the-box by Jetspeed. So I did the following: >> - I added a j2 role 'mavb-organization' to a particular user in the >> used LDAP >> - I created a directory pages/_role/mavb-organization and placed files >> home.psml and folder.metadata in it, setting the in >> folder.metadata to home.psml >> >> Now, based on a simple URL ending with /portal, I'd expect the >> profiler to look at directory pages/_role/mavb-organization for psml >> files, but it doesn't. The URL /portal/home.psml also does not lead to >> show the role specific page. >> >> I've looked at the profiler code and debugged, trying to understand it >> and get it working, but didn't succeed so far. >> The RoleCriterionResolver isn't even called, nor is >> RoleFallbackProfilingRule. What am I missing here, a wrong URL, or >> should I add/change rules or criteria in the database? >> >> Thanks >> Jeroen >> >> >> >> >> >> >> >> > From helpdesk at hippo.nl Wed Sep 17 10:05:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:11:04 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-53) Support SiteMenus which start at a certain level within the site map possibly filtered by tree as well as have a fixed or minimal number of levels opened In-Reply-To: <25509734.1209462818332.JavaMail.root@hat01> Message-ID: <9305462.1221638719558.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman reassigned PORTAL-53: ------------------------------------ Assignee: Jeroen Hoffman (was: Ate Douma) > Support SiteMenus which start at a certain level within the site map possibly filtered by tree as well as have a fixed or minimal number of levels opened > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-53 > URL: http://issues.hippo.nl/browse/PORTAL-53 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-pac > Affects Versions: 1.07.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.07.00 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 Sep 17 10:07:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:14:53 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-16) The demo-portal installation & setup instruction should be more elaborate Message-ID: <9301975.1221638839557.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman reassigned PORTAL-16: ------------------------------------ Assignee: Jeroen Hoffman (was: Ate Douma) > The demo-portal installation & setup instruction should be more elaborate > ------------------------------------------------------------------------- > > Key: PORTAL-16 > URL: http://issues.hippo.nl/browse/PORTAL-16 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > The installation/setup instructions doesn't mention that: > - JDK 1.5 is required for running the portal > - preview.localhost (and live.localhost) should be configured to map to localhost on the installation machine > - For running on Linux, instructions should be given how to set the executable bit on the required shell scripts and how to start both the repository and the portal -- 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 Sep 17 10:11:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:20:00 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-43) initial setup In-Reply-To: <27609817.1199445477217.JavaMail.jira@hat01> Message-ID: <27016222.1221639079500.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-43. ---------------------------------- Resolution: Fixed Initial setup has been done > initial setup > ------------- > > Key: PORTAL-43 > URL: http://issues.hippo.nl/browse/PORTAL-43 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal-maven-plugin > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.00 > > > - create template content for custom projects > - use common maven scripting to plugin jelly script -- 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 Sep 17 10:32:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:32:19 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-50) Role-based login configurable per site In-Reply-To: <5343691.1204911588152.JavaMail.jira@hat01> Message-ID: <23095737.1221640339523.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman updated PORTAL-50: --------------------------------- Affects Version/s: (was: 1.07.00) Fix Version/s: (was: 1.07.00) > Role-based login configurable per site > -------------------------------------- > > Key: PORTAL-50 > URL: http://issues.hippo.nl/browse/PORTAL-50 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal, hippo-portal-j2 > Reporter: Dennis Dam > Priority: Normal > > A usecase : only allow editors to see the preview site. Normal users are not able to login. -- 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 Sep 17 10:43:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:43:24 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-51) mark paths in /binaries as public In-Reply-To: <1826773.1204911708138.JavaMail.jira@hat01> Message-ID: <18126704.1221640999507.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman reassigned PORTAL-51: ------------------------------------ Assignee: Jeroen Hoffman > mark paths in /binaries as public > --------------------------------- > > Key: PORTAL-51 > URL: http://issues.hippo.nl/browse/PORTAL-51 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > -- 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 Sep 17 10:45:20 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:45:22 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-45) create dummy POM extension files in case plugin fails In-Reply-To: <27771814.1200927057167.JavaMail.jira@hat01> Message-ID: <5071475.1221641120779.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-45. ---------------------------------- Resolution: Won't Fix Maven-2 build will make the hippo plugin obsolete so this won't be fixed > create dummy POM extension files in case plugin fails > ----------------------------------------------------- > > Key: PORTAL-45 > URL: http://issues.hippo.nl/browse/PORTAL-45 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal-maven-plugin > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00 > > > avoid messages like this: > java.io.FileNotFoundException: Parent POM not found: C:\hippo\portal-project\full-portal.xml -- 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 Sep 17 10:45:20 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:45:23 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-71) check maven remote repository configuration in getting started docs In-Reply-To: <28988610.1214916064562.JavaMail.root@hat01> Message-ID: <23824437.1221641120868.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman reassigned PORTAL-71: ------------------------------------ Assignee: Jeroen Hoffman (was: Dennis Dam) > 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: Jeroen Hoffman > 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 Sep 17 10:47:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:47:20 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-44) Setup derby build&deploy procedure for getting started track In-Reply-To: <30943101.1200925437163.JavaMail.jira@hat01> Message-ID: <32895694.1221641239533.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman updated PORTAL-44: --------------------------------- Affects Version/s: 1.10.00m01 (was: 1.07.00) Assignee: Jeroen Hoffman (was: Dennis Dam) Fix Version/s: 1.10.00m01 (was: 1.07.00) > Setup derby build&deploy procedure for getting started track > ------------------------------------------------------------ > > Key: PORTAL-44 > URL: http://issues.hippo.nl/browse/PORTAL-44 > Project: Hippo Portal > Issue Type: Task > Components: hippo-portal-docs > Affects Versions: 1.10.00m01 > Reporter: Dennis Dam > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.10.00m01 > > -- 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 Sep 17 10:55:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 10:55:19 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-48) Transform sitemap document with an XSLT before parsing In-Reply-To: <15969736.1203455388146.JavaMail.jira@hat01> Message-ID: <16903223.1221641719542.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman closed PORTAL-48. -------------------------------- Resolution: Fixed After renaming XSLTTransformerService, this was fixed > 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 Sep 17 11:09:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 11:09:20 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-77) NullPointer in SiteNavigation when getting the breadcrumbs Message-ID: <3107934.1221642559718.JavaMail.jira@hat01> NullPointer in SiteNavigation when getting the breadcrumbs ---------------------------------------------------------- Key: PORTAL-77 URL: http://issues.hippo.nl/browse/PORTAL-77 Project: Hippo Portal Issue Type: Bug Components: hippo-portal-pac Affects Versions: 1.07.00 Reporter: Jeroen Hoffman Assignee: Jeroen Hoffman Priority: Normal Fix For: 1.07.00 A home item is tried to be retrieved by SiteNavigation for the breadcrumbs, and if not found on the next line homeItem.getTitle() throws the NPE. -- 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 Sep 17 12:07:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 12:07:19 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-78) When encountering a site map item with a duplicate id, warn instead of throw exception Message-ID: <28891320.1221646039438.JavaMail.jira@hat01> When encountering a site map item with a duplicate id, warn instead of throw exception -------------------------------------------------------------------------------------- Key: PORTAL-78 URL: http://issues.hippo.nl/browse/PORTAL-78 Project: Hippo Portal Issue Type: Improvement Affects Versions: 1.07.00 Reporter: Jeroen Hoffman Assignee: Jeroen Hoffman Fix For: 1.07.00 When a site map item is added and one is already there with the same id, an IllegalStateException is thrown leading to an empty site map. Change this behaviour to logging a warning, so the site map itself is still valid -- 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 Sep 17 13:23:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 13:23:20 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-52) Proxy creation in HippoPortalRegistry does not recognize interfaces declared in the registration object's class hierarchy In-Reply-To: <28879026.1205147088190.JavaMail.jira@hat01> Message-ID: <11367880.1221650599570.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-52. ------------------------------ Resolution: Won't Fix can't remember what this issue was about.. > Proxy creation in HippoPortalRegistry does not recognize interfaces declared in the registration object's class hierarchy > ------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-52 > URL: http://issues.hippo.nl/browse/PORTAL-52 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Ate Douma > Priority: Normal > Fix For: 1.07.00 > > -- 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 Sep 17 13:43:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Wed Sep 17 13:43:19 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-17) Demo portal doesn't work for intranet.localhost domain Message-ID: <12987452.1221651799545.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma reassigned PORTAL-17: ------------------------------- Assignee: Jeroen Hoffman (was: Ate Douma) Jeroen, You might want to take this up with Bart concerning a generic/shared demo hippo repository distribution which we can also use for the portal. (so: no dedicated portal demo repository anymore). Bart and I already discussed this in the past (several months back). > Demo portal doesn't work for intranet.localhost domain > ------------------------------------------------------ > > Key: PORTAL-17 > URL: http://issues.hippo.nl/browse/PORTAL-17 > Project: Hippo Portal > Issue Type: Bug > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > The provided demo-portal repository has the sitemap for the intranet site stored under /content/documents/nl/construction/sitemap.xml, but the hippo-portal.xml is configured (for both the preview and live site) to find it at /content/documents/en/construction/sitemap.xml > Resolution: > - a) provide different sitemap configurations for preview and live, or > - b) correct the default.www root in the repository and move the sitemap under /content/documents/en/construction/sitemap.xml -- 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 Sep 17 13:45:22 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Wed Sep 17 13:45:27 2008 Subject: [Hippoportal-dev] [JIRA] Assigned: (PORTAL-42) Cleanup and improve demo portal setup and configuration In-Reply-To: <3314890.1199369577178.JavaMail.jira@hat01> Message-ID: <20095110.1221651922906.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma reassigned PORTAL-42: ------------------------------- Assignee: Jeroen Hoffman (was: Ate Douma) No specific task other than properly testdrive the current described setup and configuration documentation and fix what needs fixing. > Cleanup and improve demo portal setup and configuration > ------------------------------------------------------- > > Key: PORTAL-42 > URL: http://issues.hippo.nl/browse/PORTAL-42 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > -- 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 Sep 17 15:00:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 17 15:00:20 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-51) mark paths in /binaries as public In-Reply-To: <1826773.1204911708138.JavaMail.jira@hat01> Message-ID: <25296354.1221656419526.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-51. ---------------------------------- Resolution: Fixed Added a servlet that makes a certain requests publicly available by replacing the principal with he anonymous user. > mark paths in /binaries as public > --------------------------------- > > Key: PORTAL-51 > URL: http://issues.hippo.nl/browse/PORTAL-51 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > -- 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 Sep 17 15:25:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 15:25:19 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-73) Configurable path delimiter tokens In-Reply-To: <30746391.1219659780560.JavaMail.jira@hat01> Message-ID: <19584377.1221657919501.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-73. ------------------------------ Resolution: Fixed two separators can be configured: - the sitemap detail url separator (default = ",") and - the path parameters separator (default = "/&"). This is done by assigning a PortalURLConfig object to the CMSRequestContextResolver: NOTE: if you use PortalURLConfig and you have non-default settings for either of these CMSRequestContextResolver properties; boolean mapServletPathToSitename (default = false) boolean mapServletPathToSitemapURL (default = false) boolean useDefaultSite (default = false) then you must set these values in PortalURLConfig, e.g. : Before, you would set these values as properties on CMSRequestContextResolver. > Configurable path delimiter tokens > ---------------------------------- > > Key: PORTAL-73 > URL: http://issues.hippo.nl/browse/PORTAL-73 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2 > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00 > > > Add ability to configure the characters which are used in parsing an Hippo Portal url. See question on the mailinglist from Wouter Zelle on Aug 22, 2008 (http://www.nabble.com/Sitemap-path-delimiter-cannot-be-configured-to19106230.html). Delimter tokens are now configured using static fields, this could be made configurable via Spring. -- 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 Sep 17 15:43:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 15:43:20 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-73) Configurable path delimiter tokens In-Reply-To: <30746391.1219659780560.JavaMail.jira@hat01> Message-ID: <17718061.1221658999550.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam reopened PORTAL-73: ------------------------------ needs to be fixed in the 1.10.xx branch as well > Configurable path delimiter tokens > ---------------------------------- > > Key: PORTAL-73 > URL: http://issues.hippo.nl/browse/PORTAL-73 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2 > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00, 1.10.00m01 > > > Add ability to configure the characters which are used in parsing an Hippo Portal url. See question on the mailinglist from Wouter Zelle on Aug 22, 2008 (http://www.nabble.com/Sitemap-path-delimiter-cannot-be-configured-to19106230.html). Delimter tokens are now configured using static fields, this could be made configurable via Spring. -- 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 Sep 17 15:43:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 15:43:20 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-73) Configurable path delimiter tokens In-Reply-To: <30746391.1219659780560.JavaMail.jira@hat01> Message-ID: <19484956.1221658999583.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam updated PORTAL-73: ----------------------------- Fix Version/s: 1.10.00m01 > Configurable path delimiter tokens > ---------------------------------- > > Key: PORTAL-73 > URL: http://issues.hippo.nl/browse/PORTAL-73 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2 > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00, 1.10.00m01 > > > Add ability to configure the characters which are used in parsing an Hippo Portal url. See question on the mailinglist from Wouter Zelle on Aug 22, 2008 (http://www.nabble.com/Sitemap-path-delimiter-cannot-be-configured-to19106230.html). Delimter tokens are now configured using static fields, this could be made configurable via Spring. -- 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 Sep 17 16:11:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 16:11:19 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-51) mark paths in /binaries as public In-Reply-To: <1826773.1204911708138.JavaMail.jira@hat01> Message-ID: <19986538.1221660679593.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam reopened PORTAL-51: ------------------------------ needs to be fixed in 1.10.xx branch as well > mark paths in /binaries as public > --------------------------------- > > Key: PORTAL-51 > URL: http://issues.hippo.nl/browse/PORTAL-51 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Jeroen Hoffman > Fix For: 1.07.00, 1.10.00m01 > > -- 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 Sep 17 16:11:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 16:11:20 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-51) mark paths in /binaries as public In-Reply-To: <1826773.1204911708138.JavaMail.jira@hat01> Message-ID: <15123093.1221660679625.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam updated PORTAL-51: ----------------------------- Assignee: Dennis Dam (was: Jeroen Hoffman) Fix Version/s: 1.10.00m01 > mark paths in /binaries as public > --------------------------------- > > Key: PORTAL-51 > URL: http://issues.hippo.nl/browse/PORTAL-51 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00, 1.10.00m01 > > -- 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 Sep 17 16:11:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 16:11:20 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-51) mark paths in /binaries as public In-Reply-To: <1826773.1204911708138.JavaMail.jira@hat01> Message-ID: <1275280.1221660679725.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-51. ------------------------------ Resolution: Fixed > mark paths in /binaries as public > --------------------------------- > > Key: PORTAL-51 > URL: http://issues.hippo.nl/browse/PORTAL-51 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00, 1.10.00m01 > > -- 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 Sep 17 16:13:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 17 16:13:19 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-73) Configurable path delimiter tokens In-Reply-To: <30746391.1219659780560.JavaMail.jira@hat01> Message-ID: <21553827.1221660799475.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-73. ------------------------------ Resolution: Fixed > Configurable path delimiter tokens > ---------------------------------- > > Key: PORTAL-73 > URL: http://issues.hippo.nl/browse/PORTAL-73 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2 > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00, 1.10.00m01 > > > Add ability to configure the characters which are used in parsing an Hippo Portal url. See question on the mailinglist from Wouter Zelle on Aug 22, 2008 (http://www.nabble.com/Sitemap-path-delimiter-cannot-be-configured-to19106230.html). Delimter tokens are now configured using static fields, this could be made configurable via Spring. -- 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 Thu Sep 18 09:45:20 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Thu Sep 18 09:45:17 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-78) When encountering a site map item with a duplicate id, warn instead of throw exception In-Reply-To: <28891320.1221646039438.JavaMail.jira@hat01> Message-ID: <25614788.1221723920119.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-78. ---------------------------------- Resolution: Fixed Site map items with existing id's are ignored, a warning is logged. > When encountering a site map item with a duplicate id, warn instead of throw exception > -------------------------------------------------------------------------------------- > > Key: PORTAL-78 > URL: http://issues.hippo.nl/browse/PORTAL-78 > Project: Hippo Portal > Issue Type: Improvement > Affects Versions: 1.07.00 > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > When a site map item is added and one is already there with the same id, an IllegalStateException is thrown leading to an empty site map. > Change this behaviour to logging a warning, so the site map itself is still valid -- 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 Thu Sep 18 15:39:20 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Thu Sep 18 15:39:16 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-79) Split up Portal URL and CMSRequestContext resolving Message-ID: <5084315.1221745160257.JavaMail.jira@hat01> Split up Portal URL and CMSRequestContext resolving --------------------------------------------------- Key: PORTAL-79 URL: http://issues.hippo.nl/browse/PORTAL-79 Project: Hippo Portal Issue Type: Improvement Components: hippo-portal-j2, hippo-portal-maven-plugin Reporter: Dennis Dam Assignee: Dennis Dam Priority: Normal Fix For: 1.07.00, 1.10.00m01 Currently, the portal URL and CMSRequestContext are created at the same sport: the CMSRequestContextResolver. There is a usecase where a client wants to execute some conditional logic on the portal url BEFORE the CMSRequestContext is resolved. The solution is to move the portal url creation to a separate Jetspeed valve, which is executed before the ProfilerValve (where the CMSRequestContext is created and the PSML location is determined). -- 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 Thu Sep 18 16:35:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Thu Sep 18 16:35:16 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-79) Move resolving of CMSRequestContext to valve In-Reply-To: <5084315.1221745160257.JavaMail.jira@hat01> Message-ID: <17460814.1221748519545.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam updated PORTAL-79: ----------------------------- Summary: Move resolving of CMSRequestContext to valve (was: Split up Portal URL and CMSRequestContext resolving) Description: Currently, the CMSRequestContext is resolved in the CMSRequestContextResolver, which is executed through a profiling rule by the ProfilerValve. There is a usecase from the customer where the CMSRequestContext (specifically the CMSSite object) is needed before the page location is profiled. By moving the CMSRequestContext to a separate valve (configured before the ProfilerValve), this issue can be solved. (was: Currently, the portal URL and CMSRequestContext are created at the same sport: the CMSRequestContextResolver. There is a usecase where a client wants to execute some conditional logic on the portal url BEFORE the CMSRequestContext is resolved. The solution is to move the portal url creation to a separate Jetspeed valve, which is executed before the ProfilerValve (where the CMSRequestContext is created and the PSML location is determined).) > Move resolving of CMSRequestContext to valve > -------------------------------------------- > > Key: PORTAL-79 > URL: http://issues.hippo.nl/browse/PORTAL-79 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2, hippo-portal-maven-plugin > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.00, 1.10.00m01 > > > Currently, the CMSRequestContext is resolved in the CMSRequestContextResolver, which is executed through a profiling rule by the ProfilerValve. There is a usecase from the customer where the CMSRequestContext (specifically the CMSSite object) is needed before the page location is profiled. By moving the CMSRequestContext to a separate valve (configured before the ProfilerValve), this issue can be solved. -- 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 Fri Sep 19 09:53:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Fri Sep 19 10:01:58 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-79) Move resolving of CMSRequestContext to valve In-Reply-To: <5084315.1221745160257.JavaMail.jira@hat01> Message-ID: <27768386.1221810799501.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38719 ] Dennis Dam commented on PORTAL-79: ---------------------------------- To get the new setup to work, the assembly Spring files "pipelines.xml" and "profiler.xml" must be updated, as well as the initial DB seed (j2-seed.xml). Because the DB seed changed, obviously the DB needs to be re-initialized with "maven hp:init-portal-db". The default contents of these files are available in the Hippo-Portal Maven 1 plugin : http://svn.hippocms.org/repos/hippo/hippo-portal/trunk/hippo-portal-maven-plugin/src/plugin-resources/portal/template/src/webapp/WEB-INF/assembly/override/pipelines.xml http://svn.hippocms.org/repos/hippo/hippo-portal/trunk/hippo-portal-maven-plugin/src/plugin-resources/portal/template/src/webapp/WEB-INF/assembly/override/profiler.xml http://svn.hippocms.org/repos/hippo/hippo-portal/trunk/hippo-portal-maven-plugin/src/plugin-resources/portal/template/template/src/sql/min/j2-seed.xml Only one line changed in j2-seed.xml : from : to: > Move resolving of CMSRequestContext to valve > -------------------------------------------- > > Key: PORTAL-79 > URL: http://issues.hippo.nl/browse/PORTAL-79 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2, hippo-portal-maven-plugin > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.00, 1.10.00m01 > > > Currently, the CMSRequestContext is resolved in the CMSRequestContextResolver, which is executed through a profiling rule by the ProfilerValve. There is a usecase from the customer where the CMSRequestContext (specifically the CMSSite object) is needed before the page location is profiled. By moving the CMSRequestContext to a separate valve (configured before the ProfilerValve), this issue can be solved. -- 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 Fri Sep 19 09:56:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Fri Sep 19 10:02:07 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-73) Configurable path delimiter tokens In-Reply-To: <30746391.1219659780560.JavaMail.jira@hat01> Message-ID: <11587970.1221810979479.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38720 ] Dennis Dam commented on PORTAL-73: ---------------------------------- the above configuration changed somewhat.. the PortalURLConfig is not wired to CMSRequestContextResolver anymore, but to CMSRequestContextValve. See issue PORTAL-79 for more details. > Configurable path delimiter tokens > ---------------------------------- > > Key: PORTAL-73 > URL: http://issues.hippo.nl/browse/PORTAL-73 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2 > Affects Versions: 1.07.00 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00, 1.10.00m01 > > > Add ability to configure the characters which are used in parsing an Hippo Portal url. See question on the mailinglist from Wouter Zelle on Aug 22, 2008 (http://www.nabble.com/Sitemap-path-delimiter-cannot-be-configured-to19106230.html). Delimter tokens are now configured using static fields, this could be made configurable via Spring. -- 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 Fri Sep 19 13:35:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Fri Sep 19 13:35:21 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-80) Set a type on CMSRequestContext to enable setting HTTP status code 404 Message-ID: <16890404.1221824119604.JavaMail.jira@hat01> Set a type on CMSRequestContext to enable setting HTTP status code 404 ----------------------------------------------------------------------- Key: PORTAL-80 URL: http://issues.hippo.nl/browse/PORTAL-80 Project: Hippo Portal Issue Type: Improvement Components: hippo-portal, hippo-portal-api Affects Versions: 1.07.00, 1.10.00m01 Reporter: Jeroen Hoffman Assignee: Jeroen Hoffman Fix For: 1.07.00, 1.10.00m01 Patch supplied by ddam -- 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 Fri Sep 19 16:16:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Fri Sep 19 16:16:20 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-80) Set a type on CMSRequestContext to enable setting HTTP status code 404 In-Reply-To: <16890404.1221824119604.JavaMail.jira@hat01> Message-ID: <9846220.1221833779498.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman updated PORTAL-80: --------------------------------- Component/s: hippo-portal-j2 > Set a type on CMSRequestContext to enable setting HTTP status code 404 > ----------------------------------------------------------------------- > > Key: PORTAL-80 > URL: http://issues.hippo.nl/browse/PORTAL-80 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Affects Versions: 1.07.00, 1.10.00m01 > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Fix For: 1.07.00, 1.10.00m01 > > > Patch supplied by ddam -- 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 Fri Sep 19 16:54:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Fri Sep 19 16:54:20 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-80) Set a type on CMSRequestContext to enable setting HTTP status code 404 In-Reply-To: <16890404.1221824119604.JavaMail.jira@hat01> Message-ID: <14362350.1221836059498.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-80. ---------------------------------- Resolution: Fixed Introduce an UrlType enum (NORMAL, DEFAULT, LOGIN, PAGENOTFOUND, ACCEPT_TERMS) in CMSRequestContext. The PAGENOTFOUND is used in the context valve to set a 404 response header. > Set a type on CMSRequestContext to enable setting HTTP status code 404 > ----------------------------------------------------------------------- > > Key: PORTAL-80 > URL: http://issues.hippo.nl/browse/PORTAL-80 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Affects Versions: 1.07.00, 1.10.00m01 > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Fix For: 1.07.00, 1.10.00m01 > > > Patch supplied by ddam -- 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 Tue Sep 23 10:27:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:27:28 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (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: <8230358.1222158439626.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma closed PORTAL-65. --------------------------- Resolution: Fixed Done > 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 helpdesk at hippo.nl Tue Sep 23 10:27:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:27:29 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-64) restructure the project src folders according to maven-2 conventions In-Reply-To: <4986215.1212752210406.JavaMail.root@hat01> Message-ID: <1154499.1222158439684.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma closed PORTAL-64. --------------------------- Resolution: Fixed Done > restructure the project src folders according to maven-2 conventions > -------------------------------------------------------------------- > > Key: PORTAL-64 > URL: http://issues.hippo.nl/browse/PORTAL-64 > Project: Hippo Portal > Issue Type: Sub-task > Affects Versions: 1.10.00m01 > Reporter: Ate Douma > Assignee: Dennis Dam > Fix For: 1.10.00m01 > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > -- 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 Tue Sep 23 10:29:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:29:20 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-66) provide maven-2 plugin configurations with corresponding features as the hippo-portal-maven-plugin for Hippo Portal 1.0x In-Reply-To: <27233620.1212752334814.JavaMail.root@hat01> Message-ID: <24639110.1222158559505.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma closed PORTAL-66. --------------------------- Resolution: Fixed The new jetspeed:mvn plugin already covers the basic requirements, no need (yet) to provide one for Hippo Portal > provide maven-2 plugin configurations with corresponding features as the hippo-portal-maven-plugin for Hippo Portal 1.0x > ------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-66 > URL: http://issues.hippo.nl/browse/PORTAL-66 > 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 helpdesk at hippo.nl Tue Sep 23 10:31:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:31:20 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-67) provide new demo portal using maven-2 In-Reply-To: <11625012.1212752450396.JavaMail.root@hat01> Message-ID: <10557651.1222158679474.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-67: ---------------------------- Affects Version/s: 1.10.00.m02 (was: 1.10.00m01) > provide new demo portal using maven-2 > ------------------------------------- > > Key: PORTAL-67 > URL: http://issues.hippo.nl/browse/PORTAL-67 > Project: Hippo Portal > Issue Type: Sub-task > Affects Versions: 1.10.00.m02 > Reporter: Ate Douma > Assignee: Ate Douma > Fix For: 1.10.00m01 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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 Tue Sep 23 10:32:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:32:19 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-68) Update the site documentation for the new maven-2 and jetspeed-2.2 build In-Reply-To: <19388237.1212752450437.JavaMail.root@hat01> Message-ID: <23459093.1222158739947.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-68: ---------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > Update the site documentation for the new maven-2 and jetspeed-2.2 build > ------------------------------------------------------------------------ > > Key: PORTAL-68 > URL: http://issues.hippo.nl/browse/PORTAL-68 > Project: Hippo Portal > Issue Type: Sub-task > Affects Versions: 1.10.00m01 > Reporter: Ate Douma > Fix For: 1.10.00.m02 > > Original Estimate: 4 days > Remaining Estimate: 4 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 helpdesk at hippo.nl Tue Sep 23 10:34:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:34:20 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-81) Provide demo and documentation for the new maven-2 and Jetspeed-2.2 based build Message-ID: <9028373.1222158859667.JavaMail.jira@hat01> Provide demo and documentation for the new maven-2 and Jetspeed-2.2 based build -------------------------------------------------------------------------------- Key: PORTAL-81 URL: http://issues.hippo.nl/browse/PORTAL-81 Project: Hippo Portal Issue Type: Task Components: demo-pa, demo-portal, demo-portal-installer, hippo-portal-docs Affects Versions: 1.10.00m01 Reporter: Ate Douma Fix For: 1.10.00.m02 -- 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 Tue Sep 23 10:34:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:34:21 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-67) provide new demo portal using maven-2 In-Reply-To: <11625012.1212752450396.JavaMail.root@hat01> Message-ID: <25066854.1222158859707.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-67: ---------------------------- Affects Version/s: 1.10.00m01 (was: 1.10.00.m02) Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > provide new demo portal using maven-2 > ------------------------------------- > > Key: PORTAL-67 > URL: http://issues.hippo.nl/browse/PORTAL-67 > Project: Hippo Portal > Issue Type: Sub-task > Affects Versions: 1.10.00m01 > Reporter: Ate Douma > Assignee: Ate Douma > Fix For: 1.10.00.m02 > > Original Estimate: 1 day > Remaining Estimate: 1 day > -- 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 Tue Sep 23 10:36:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:36:19 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-62) Migrate build to maven-2 and Jetspeed-2.2 In-Reply-To: <28082219.1212751975454.JavaMail.root@hat01> Message-ID: <23400387.1222158979488.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma closed PORTAL-62. --------------------------- Resolution: Fixed Done > Migrate build to maven-2 and Jetspeed-2.2 > ----------------------------------------- > > Key: PORTAL-62 > URL: http://issues.hippo.nl/browse/PORTAL-62 > Project: Hippo Portal > Issue Type: Task > Affects Versions: 1.10.00m01 > Reporter: Ate Douma > Assignee: Ate Douma > Fix For: 1.10.00m01 > > -- 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 Tue Sep 23 10:36:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:36:20 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-29) Sitemap item authentication based on roles In-Reply-To: <28901921.1184680834000.JavaMail.jira@hat01> Message-ID: <4235965.1222158979569.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-29: ---------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > Sitemap item authentication based on roles > ------------------------------------------ > > Key: PORTAL-29 > URL: http://issues.hippo.nl/browse/PORTAL-29 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.10.00.m02 > > > In backend: > * assign roles on sitemap items (based on LDAP / Slide whatever) > > In Portal: > * current set of roles to check against needs to be "pluggable", e.g. "rolesContainer".hasRole(), default implemented using request.isUserInRole() > * prohobit access to forbidden urls > * filter sitemenu items -- 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 Tue Sep 23 10:38:20 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:38:21 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-70) White Label Portal functionality using either "organization" based "site" prefixing or direct domain mapping In-Reply-To: <23597498.1214407204577.JavaMail.root@hat01> Message-ID: <28405449.1222159100084.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-70: ---------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > White Label Portal functionality using either "organization" based "site" prefixing or direct domain mapping > ------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-70 > URL: http://issues.hippo.nl/browse/PORTAL-70 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Ate Douma > Assignee: Dennis Dam > Fix For: 1.10.00.m02 > > > A "White Label" Portal providing "organization" based functionality and/or Look&Feel should be possible using either: > - domain (prefix) mapping: derive "organization" from the incoming request host using a specific format, e.g. like .mydomain: > - site prefixing: // > When using site prefixing, it must be possible to disable/enable this for a domain, allowing both/combined usage of something like: > www.mydomain.com/customer/site and customer.mydomain.com/site > For access and usage of the derived "organization" we need a pluggable factory to allow third party implementation of (at least) the following methods: > boolean hasRole() > boolean isMember(User) // to determine if the current user is authorized to access this organization "view" of the Portal. > The current CMSRequestContext interface needs to be extended to provide access to the derived "organization" (if available) -- 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 Tue Sep 23 10:38:20 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:38:22 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-74) Nested sitemap support In-Reply-To: <15867008.1219744920599.JavaMail.jira@hat01> Message-ID: <25655516.1222159100124.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-74: ---------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > Nested sitemap support > ---------------------- > > Key: PORTAL-74 > URL: http://issues.hippo.nl/browse/PORTAL-74 > Project: Hippo Portal > Issue Type: New Feature > Components: hippo-portal > Affects Versions: 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.10.00.m02 > > Attachments: hippo-portal-child-sitemap.diff > > > A contribution of Michiel Trimpe from Aug 25, 2008 on the Hippo Portal dev list. His mail: > --- > Hey there, > Something else tangentially related to the last post. > Due to what ended up being miscommunication I developed some functionality for the SiteMapLoader to include another SiteMap at some point in it's tree by adding a 'child-sitemap' attribute on a SiteMapItem. We won't be using it in our implementation but perhaps you might still want to use it in Hippo Portal. > The diff is attached to the email. > Regards, > Michiel Trimpe > --- -- 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 Tue Sep 23 10:38:20 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:38:23 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-44) Setup derby build&deploy procedure for getting started track In-Reply-To: <30943101.1200925437163.JavaMail.jira@hat01> Message-ID: <11814656.1222159100318.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-44: ---------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > Setup derby build&deploy procedure for getting started track > ------------------------------------------------------------ > > Key: PORTAL-44 > URL: http://issues.hippo.nl/browse/PORTAL-44 > Project: Hippo Portal > Issue Type: Task > Components: hippo-portal-docs > Affects Versions: 1.10.00m01 > Reporter: Dennis Dam > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.10.00.m02 > > -- 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 Tue Sep 23 10:38:20 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:38:24 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-75) Dynamic PSML resolving In-Reply-To: <32346797.1220271360757.JavaMail.jira@hat01> Message-ID: <7165455.1222159100187.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-75: ---------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > Dynamic PSML resolving > ---------------------- > > Key: PORTAL-75 > URL: http://issues.hippo.nl/browse/PORTAL-75 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2 > Affects Versions: 1.07.00, 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.00, 1.10.00.m02 > > > Currently, the resolved location of a psml is based on the type of the resolved sitemap item. This feature would add the ability to override the default location of the PSML, which could be derived from the resolved CMSRequestContext. > An existing usecase is to fetch the type of the associated detail document (the type is stored as webdav property), and use that to locate the PSML. This would allow mapping detail urls under 1 sitemap item to different PSMLs. -- 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 Tue Sep 23 10:40:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 10:40:23 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-44) Setup derby build&deploy procedure for getting started track In-Reply-To: <30943101.1200925437163.JavaMail.jira@hat01> Message-ID: <17629146.1222159219559.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-44: ---------------------------- Parent: PORTAL-81 Issue Type: Sub-task (was: Task) > Setup derby build&deploy procedure for getting started track > ------------------------------------------------------------ > > Key: PORTAL-44 > URL: http://issues.hippo.nl/browse/PORTAL-44 > Project: Hippo Portal > Issue Type: Sub-task > Components: hippo-portal-docs > Affects Versions: 1.10.00m01 > Reporter: Dennis Dam > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.10.00.m02 > > -- 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 Tue Sep 23 14:25:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Tue Sep 23 14:25:19 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-79) Move resolving of CMSRequestContext to valve In-Reply-To: <5084315.1221745160257.JavaMail.jira@hat01> Message-ID: <25779924.1222172719517.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-79. ------------------------------ Resolution: Fixed > Move resolving of CMSRequestContext to valve > -------------------------------------------- > > Key: PORTAL-79 > URL: http://issues.hippo.nl/browse/PORTAL-79 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2, hippo-portal-maven-plugin > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.00, 1.10.00m01 > > > Currently, the CMSRequestContext is resolved in the CMSRequestContextResolver, which is executed through a profiling rule by the ProfilerValve. There is a usecase from the customer where the CMSRequestContext (specifically the CMSSite object) is needed before the page location is profiled. By moving the CMSRequestContext to a separate valve (configured before the ProfilerValve), this issue can be solved. -- 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 Tue Sep 23 15:16:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Tue Sep 23 15:16:19 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-75) Dynamic PSML resolving In-Reply-To: <32346797.1220271360757.JavaMail.jira@hat01> Message-ID: <29152170.1222175779481.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma closed PORTAL-75. --------------------------- Fix Version/s: (was: 1.10.00.m02) Resolution: Won't Fix With the latest changes which spitted up the resolving of the CMSRequestContext from the PageResolving itself, implementing this rather highly custom feature, is now easy to implement according to specific custom needs. Providing this feature generically however is much more difficult and therefore won't be done (for now). Closing as "Won't Fix" > Dynamic PSML resolving > ---------------------- > > Key: PORTAL-75 > URL: http://issues.hippo.nl/browse/PORTAL-75 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-j2 > Affects Versions: 1.07.00, 1.10.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.07.00 > > > Currently, the resolved location of a psml is based on the type of the resolved sitemap item. This feature would add the ability to override the default location of the PSML, which could be derived from the resolved CMSRequestContext. > An existing usecase is to fetch the type of the associated detail document (the type is stored as webdav property), and use that to locate the PSML. This would allow mapping detail urls under 1 sitemap item to different PSMLs. -- 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 Sep 24 10:06:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 24 10:09:13 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-82) Upgrade 1.10.00 branch to Jetspeed snapshot Message-ID: <18049513.1222243579444.JavaMail.jira@hat01> Upgrade 1.10.00 branch to Jetspeed snapshot ------------------------------------------- Key: PORTAL-82 URL: http://issues.hippo.nl/browse/PORTAL-82 Project: Hippo Portal Issue Type: Task Components: hippo-portal-j2 Affects Versions: 1.10.00.m02 Reporter: Dennis Dam Assignee: Dennis Dam Priority: Normal Fix For: 1.10.00.m02 Some refactoring efforts are required to upgrade to the latest snapshot of Jetspeed, mainly concerning the refactored Jetspeed security implementation. -- 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 Sep 24 10:08:20 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 24 10:11:54 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-82) Upgrade 1.10.00 branch to Jetspeed snapshot In-Reply-To: <18049513.1222243579444.JavaMail.jira@hat01> Message-ID: <11725611.1222243700102.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38847 ] Dennis Dam commented on PORTAL-82: ---------------------------------- As part of the upgrade, the NTLM package will be removed as well, since that is now part of Jetspeed > Upgrade 1.10.00 branch to Jetspeed snapshot > ------------------------------------------- > > Key: PORTAL-82 > URL: http://issues.hippo.nl/browse/PORTAL-82 > Project: Hippo Portal > Issue Type: Task > Components: hippo-portal-j2 > Affects Versions: 1.10.00.m02 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.10.00.m02 > > > Some refactoring efforts are required to upgrade to the latest snapshot of Jetspeed, mainly concerning the refactored Jetspeed security implementation. -- 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 Sep 24 10:10:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 24 10:14:02 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-82) Upgrade 1.10.00 branch to Jetspeed 2.2 snapshot In-Reply-To: <18049513.1222243579444.JavaMail.jira@hat01> Message-ID: <20755731.1222243819505.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam updated PORTAL-82: ----------------------------- Summary: Upgrade 1.10.00 branch to Jetspeed 2.2 snapshot (was: Upgrade 1.10.00 branch to Jetspeed snapshot) > Upgrade 1.10.00 branch to Jetspeed 2.2 snapshot > ----------------------------------------------- > > Key: PORTAL-82 > URL: http://issues.hippo.nl/browse/PORTAL-82 > Project: Hippo Portal > Issue Type: Task > Components: hippo-portal-j2 > Affects Versions: 1.10.00.m02 > Reporter: Dennis Dam > Assignee: Dennis Dam > Priority: Normal > Fix For: 1.10.00.m02 > > > Some refactoring efforts are required to upgrade to the latest snapshot of Jetspeed, mainly concerning the refactored Jetspeed security implementation. -- 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 Sep 24 13:44:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 24 13:44:20 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-77) NullPointer in SiteNavigation when getting the breadcrumbs In-Reply-To: <3107934.1221642559718.JavaMail.jira@hat01> Message-ID: <14268519.1222256659966.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-77. ---------------------------------- Fix Version/s: 1.10.00m01 Resolution: Fixed Check for the presence of an item named 'home' to avoid the nullpointer > NullPointer in SiteNavigation when getting the breadcrumbs > ---------------------------------------------------------- > > Key: PORTAL-77 > URL: http://issues.hippo.nl/browse/PORTAL-77 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal-pac > Affects Versions: 1.07.00 > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.07.00, 1.10.00m01 > > > A home item is tried to be retrieved by SiteNavigation for the breadcrumbs, and if not found on the next line homeItem.getTitle() throws the NPE. -- 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 j.hoffman at onehippo.com Wed Sep 24 13:45:44 2008 From: j.hoffman at onehippo.com (Jeroen Hoffman) Date: Wed Sep 24 13:45:45 2008 Subject: [Hippoportal-dev] NullPointer when using BreadCrumbPortlet In-Reply-To: <48CF67D4.6010006@onehippo.com> References: <19265854.post@talk.nabble.com> <19506576.post@talk.nabble.com> <48CF67D4.6010006@onehippo.com> Message-ID: <48DA2868.3050709@onehippo.com> This has now been resolved in issue http://issues.hippo.nl/browse/PORTAL-77 Jeroen Hoffman Dennis Dam schreef: > Sorry Willem, it seems like I totally overlooked your question. To > answer your question, the line > > cmsRequestContext.getSiteMapItem().getSiteMap().getById("home"); > > > will look up an "item" with id "home" in sitemap.xml. So the value > "home" is not in a property, but is the value of the ID element of a > "fixed-item" or (exclusive) menu-item fetched in the sitemap document. > > hth, > > Dennis > > > > > Willem Vermeer wrote: >> Can anybody help me on this one? >> Thanks, >> Willem >> >> > > _______________________________________________ > Hippoportal-dev mailing list > Hippoportal-dev@lists.hippo.nl > http://lists.hippo.nl/mailman/listinfo/hippoportal-dev From helpdesk at hippo.nl Wed Sep 24 14:13:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 24 14:13:19 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-83) Bug in resolving sitepart used to create final portal url Message-ID: <26946007.1222258399453.JavaMail.jira@hat01> Bug in resolving sitepart used to create final portal url --------------------------------------------------------- Key: PORTAL-83 URL: http://issues.hippo.nl/browse/PORTAL-83 Project: Hippo Portal Issue Type: Bug Components: hippo-portal, hippo-portal-api, hippo-portal-j2 Affects Versions: 1.07.00, 1.10.00m01, 1.10.00.m02, 2.01.00m01 Reporter: Dennis Dam Assignee: Dennis Dam Fix For: 1.07.00, 1.10.00.m02 this bug occurs when: - "useDefaultSite" flag in PortalURLConfig is false - the user navigates to the default url / (i.e.: the url does not contain a site id!) - a default site is configured for the current Domain. The problem was that the sitename was not used to create the final portal url in CMSApplicationRegistryImpl. This is solved by checking if the original portal url was created with useDefaultSite = false, and in that case using the default site name associated with the Domain. -- 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 Sep 24 14:47:19 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Wed Sep 24 14:47:39 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-83) Bug in resolving sitepart used to create final portal url In-Reply-To: <26946007.1222258399453.JavaMail.jira@hat01> Message-ID: <18721181.1222260439508.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam resolved PORTAL-83. ------------------------------ Resolution: Fixed > Bug in resolving sitepart used to create final portal url > --------------------------------------------------------- > > Key: PORTAL-83 > URL: http://issues.hippo.nl/browse/PORTAL-83 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal, hippo-portal-api, hippo-portal-j2 > Affects Versions: 1.07.00, 1.10.00m01, 1.10.00.m02, 2.01.00m01 > Reporter: Dennis Dam > Assignee: Dennis Dam > Fix For: 1.07.00, 1.10.00.m02 > > > this bug occurs when: > - "useDefaultSite" flag in PortalURLConfig is false > - the user navigates to the default url / (i.e.: the url does not contain a site id!) > - a default site is configured for the current Domain. > The problem was that the sitename was not used to create the final portal url in CMSApplicationRegistryImpl. This is solved by checking if the original portal url was created with useDefaultSite = false, and in that case using the default site name associated with the Domain. -- 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 Sep 24 15:44:19 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Wed Sep 24 15:44:19 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-53) Support SiteMenus which start at a certain level within the site map possibly filtered by tree as well as have a fixed or minimal number of levels opened In-Reply-To: <25509734.1209462818332.JavaMail.root@hat01> Message-ID: <17710855.1222263859545.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-53. ---------------------------------- Fix Version/s: 1.10.00m01 Resolution: Fixed Applied patch given by a customer portal developer. - nr of requested levels may be 0 - stop looping child items sooner, if startlevel equals endlevel > Support SiteMenus which start at a certain level within the site map possibly filtered by tree as well as have a fixed or minimal number of levels opened > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-53 > URL: http://issues.hippo.nl/browse/PORTAL-53 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-pac > Affects Versions: 1.07.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.07.00, 1.10.00m01 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 Sep 24 15:46:19 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Wed Sep 24 16:40:32 2008 Subject: [Hippoportal-dev] [JIRA] Updated: (PORTAL-53) Support SiteMenus which start at a certain level within the site map possibly filtered by tree as well as have a fixed or minimal number of levels opened In-Reply-To: <25509734.1209462818332.JavaMail.root@hat01> Message-ID: <32394808.1222263979501.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ate Douma updated PORTAL-53: ---------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) > Support SiteMenus which start at a certain level within the site map possibly filtered by tree as well as have a fixed or minimal number of levels opened > ---------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-53 > URL: http://issues.hippo.nl/browse/PORTAL-53 > Project: Hippo Portal > Issue Type: Improvement > Components: hippo-portal-pac > Affects Versions: 1.07.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.07.00, 1.10.00.m02 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > -- 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 Thu Sep 25 11:17:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Thu Sep 25 11:17:42 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-77) NullPointer in SiteNavigation when getting the breadcrumbs In-Reply-To: <3107934.1221642559718.JavaMail.jira@hat01> Message-ID: <24953267.1222334258135.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman reopened PORTAL-77: ---------------------------------- lost some functionality while avoiding nullpointer in adding home item if the top wasn't "home" > NullPointer in SiteNavigation when getting the breadcrumbs > ---------------------------------------------------------- > > Key: PORTAL-77 > URL: http://issues.hippo.nl/browse/PORTAL-77 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal-pac > Affects Versions: 1.07.00 > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.07.00, 1.10.00m01 > > > A home item is tried to be retrieved by SiteNavigation for the breadcrumbs, and if not found on the next line homeItem.getTitle() throws the NPE. -- 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 Thu Sep 25 11:19:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Thu Sep 25 11:19:38 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-77) NullPointer in SiteNavigation when getting the breadcrumbs In-Reply-To: <3107934.1221642559718.JavaMail.jira@hat01> Message-ID: <1928638.1222334378089.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-77. ---------------------------------- Fix Version/s: 1.10.00.m02 (was: 1.10.00m01) Resolution: Fixed Fixed the lost functionality > NullPointer in SiteNavigation when getting the breadcrumbs > ---------------------------------------------------------- > > Key: PORTAL-77 > URL: http://issues.hippo.nl/browse/PORTAL-77 > Project: Hippo Portal > Issue Type: Bug > Components: hippo-portal-pac > Affects Versions: 1.07.00 > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Priority: Normal > Fix For: 1.07.00, 1.10.00.m02 > > > A home item is tried to be retrieved by SiteNavigation for the breadcrumbs, and if not found on the next line homeItem.getTitle() throws the NPE. -- 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 Thu Sep 25 22:28:38 2008 From: helpdesk at hippo.nl (JIRA (Ate Douma)) Date: Thu Sep 25 22:28:37 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-17) Demo portal doesn't work for intranet.localhost domain Message-ID: <4344067.1222374518156.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38968 ] Ate Douma commented on PORTAL-17: --------------------------------- Jeroen, If creating a new demo-repository is going to take too much time right now (because we'd then want it to be a standard demo repository shared between several other Hippo Projects), resolving this one using option a) would be fine for me too (e.g. only change the demo portal sitemap configuration). > Demo portal doesn't work for intranet.localhost domain > ------------------------------------------------------ > > Key: PORTAL-17 > URL: http://issues.hippo.nl/browse/PORTAL-17 > Project: Hippo Portal > Issue Type: Bug > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > The provided demo-portal repository has the sitemap for the intranet site stored under /content/documents/nl/construction/sitemap.xml, but the hippo-portal.xml is configured (for both the preview and live site) to find it at /content/documents/en/construction/sitemap.xml > Resolution: > - a) provide different sitemap configurations for preview and live, or > - b) correct the default.www root in the repository and move the sitemap under /content/documents/en/construction/sitemap.xml -- 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 nico.tromp at gmail.com Fri Sep 26 10:29:23 2008 From: nico.tromp at gmail.com (Nico Tromp) Date: Fri Sep 26 10:29:26 2008 Subject: [Hippoportal-dev] LinkFactory not handling alternative links Message-ID: <439bd37e0809260129s2e505fe2l937971dd99aaeefd@mail.gmail.com> Hi all. I ran into the next problem. I'm not sure if this is a bug, in my opinion it is. In the sitemenu we have entries like the following: DemoName Demo /content/documents/demo.xml DirectoryDemo Directory Demo /appdata/demo/samples In the repository we have directories and files beneath: /appdata/demo/samples When I generate the links for the web-page I need a transformation from repository href property values like: /appdata/demo/samples/sample1/content.xml to links with a comma like: /Demo/DirectoryDemo,/sample1/content.xml When I use the following code I just get the original URL back. CMSLinkFactory linkFactory = getCMSRequestContext().getLinkFactory(); String href = "/appdata/demo/samples/sample1/content.xml"; LinkItem linkToProduct = linkFactory.createLinkItem(request, response, "", href); When I do the same for files that reside somewhere beneath '/content/' and adjust the code/DASL queries accordingly I do get a LinkItem that contains a comma. It would be nice if the LinkFactory, CMSLinkFactoryImpl to be precise, is not tied/hard wired to files beneath '/content/'. So my question is: is it possible to use the LinkFactory for creating the desired links? Thanks in advance Nico Tromp -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080926/1da299eb/attachment.htm From d.dam at onehippo.com Fri Sep 26 11:03:28 2008 From: d.dam at onehippo.com (Dennis Dam) Date: Fri Sep 26 11:03:29 2008 Subject: [Hippoportal-dev] LinkFactory not handling alternative links In-Reply-To: <439bd37e0809260129s2e505fe2l937971dd99aaeefd@mail.gmail.com> References: <439bd37e0809260129s2e505fe2l937971dd99aaeefd@mail.gmail.com> Message-ID: <48DCA560.1070208@onehippo.com> Hi Nico, You could also move the appdata folder to the /content folder, and then remove read rights for normal users (i.e. non-root users for example), so that they can't see and edit those documents. The path /content is a standardized path, which I would recommend using (same goes for /binaries). regards, Dennis Nico Tromp wrote: > Hi all. > > > I ran into the next problem. I'm not sure if this is a bug, in my > opinion it is. > > In the sitemenu we have entries like the following: > > DemoName > Demo > /content/documents/demo.xml > > > DirectoryDemo > Directory Demo > /appdata/demo/samples > > > > > In the repository we have directories and files beneath: > /appdata/demo/samples > > When I generate the links for the web-page I need a transformation > from repository href property values like: > /appdata/demo/samples/sample1/content.xml > to links with a comma like: > /Demo/DirectoryDemo,/sample1/content.xml > > When I use the following code I just get the original URL back. > > CMSLinkFactory linkFactory = getCMSRequestContext().getLinkFactory(); > String href = "/appdata/demo/samples/sample1/content.xml"; > LinkItem linkToProduct = linkFactory.createLinkItem(request, response, > "", href); > > When I do the same for files that reside somewhere beneath '/content/' > and adjust the code/DASL queries accordingly I do get a LinkItem that > contains a comma. > > It would be nice if the LinkFactory, CMSLinkFactoryImpl to be precise, > is not tied/hard wired to files beneath '/content/'. > > So my question is: is it possible to use the LinkFactory for creating > the desired links? > > > Thanks in advance > > Nico Tromp > ------------------------------------------------------------------------ > > _______________________________________________ > Hippoportal-dev mailing list > Hippoportal-dev@lists.hippo.nl > http://lists.hippo.nl/mailman/listinfo/hippoportal-dev > From nico.tromp at gmail.com Fri Sep 26 11:50:02 2008 From: nico.tromp at gmail.com (Nico Tromp) Date: Fri Sep 26 11:50:52 2008 Subject: [Hippoportal-dev] LinkFactory not handling alternative links In-Reply-To: <48DCA560.1070208@onehippo.com> References: <439bd37e0809260129s2e505fe2l937971dd99aaeefd@mail.gmail.com> <48DCA560.1070208@onehippo.com> Message-ID: <439bd37e0809260250s479a4a3agcb34f84087d9d703@mail.gmail.com> Thanks Dennis for the quick response. We are already in the process of making the changes you suggested. Kind regards Nico On Fri, Sep 26, 2008 at 11:03 AM, Dennis Dam wrote: > Hi Nico, > > You could also move the appdata folder to the /content folder, and then > remove read rights for normal users (i.e. non-root users for example), so > that they can't see and edit those documents. The path /content is a > standardized path, which I would recommend using (same goes for /binaries). > > regards, > Dennis > > Nico Tromp wrote: > >> Hi all. >> >> >> I ran into the next problem. I'm not sure if this is a bug, in my opinion >> it is. >> >> In the sitemenu we have entries like the following: >> >> DemoName >> Demo >> /content/documents/demo.xml >> >> >> DirectoryDemo >> Directory Demo >> /appdata/demo/samples >> >> >> >> >> In the repository we have directories and files beneath: >> /appdata/demo/samples >> >> When I generate the links for the web-page I need a transformation from >> repository href property values like: >> /appdata/demo/samples/sample1/content.xml >> to links with a comma like: >> /Demo/DirectoryDemo,/sample1/content.xml >> >> When I use the following code I just get the original URL back. >> >> CMSLinkFactory linkFactory = getCMSRequestContext().getLinkFactory(); >> String href = "/appdata/demo/samples/sample1/content.xml"; >> LinkItem linkToProduct = linkFactory.createLinkItem(request, response, "", >> href); >> >> When I do the same for files that reside somewhere beneath '/content/' and >> adjust the code/DASL queries accordingly I do get a LinkItem that contains a >> comma. >> >> It would be nice if the LinkFactory, CMSLinkFactoryImpl to be precise, is >> not tied/hard wired to files beneath '/content/'. >> >> So my question is: is it possible to use the LinkFactory for creating the >> desired links? >> >> >> Thanks in advance >> >> Nico Tromp >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> 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 -------------- An HTML attachment was scrubbed... URL: http://lists.hippo.nl/pipermail/hippoportal-dev/attachments/20080926/991904e9/attachment.htm From helpdesk at hippo.nl Mon Sep 29 09:40:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 09:40:40 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-17) Demo portal doesn't work for intranet.localhost domain Message-ID: <8999361.1222674038550.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39037 ] Jeroen Hoffman commented on PORTAL-17: -------------------------------------- OK I'll change the configuration, we want a quick release > Demo portal doesn't work for intranet.localhost domain > ------------------------------------------------------ > > Key: PORTAL-17 > URL: http://issues.hippo.nl/browse/PORTAL-17 > Project: Hippo Portal > Issue Type: Bug > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > The provided demo-portal repository has the sitemap for the intranet site stored under /content/documents/nl/construction/sitemap.xml, but the hippo-portal.xml is configured (for both the preview and live site) to find it at /content/documents/en/construction/sitemap.xml > Resolution: > - a) provide different sitemap configurations for preview and live, or > - b) correct the default.www root in the repository and move the sitemap under /content/documents/en/construction/sitemap.xml -- 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 Mon Sep 29 11:09:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 11:10:10 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-17) Demo portal doesn't work for intranet.localhost domain Message-ID: <4349116.1222679378625.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-17. ---------------------------------- Resolution: Fixed Changed configuration to match the location of live sitemap. Also needed checks on empty resultset for news in freemarker templates, as the live branch has no news included. > Demo portal doesn't work for intranet.localhost domain > ------------------------------------------------------ > > Key: PORTAL-17 > URL: http://issues.hippo.nl/browse/PORTAL-17 > Project: Hippo Portal > Issue Type: Bug > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > The provided demo-portal repository has the sitemap for the intranet site stored under /content/documents/nl/construction/sitemap.xml, but the hippo-portal.xml is configured (for both the preview and live site) to find it at /content/documents/en/construction/sitemap.xml > Resolution: > - a) provide different sitemap configurations for preview and live, or > - b) correct the default.www root in the repository and move the sitemap under /content/documents/en/construction/sitemap.xml -- 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 Mon Sep 29 15:24:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 15:24:38 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-42) Cleanup and improve demo portal setup and configuration In-Reply-To: <3314890.1199369577178.JavaMail.jira@hat01> Message-ID: <16019907.1222694678177.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-42. ---------------------------------- Resolution: Fixed Improved the portal-demo documentation > Cleanup and improve demo portal setup and configuration > ------------------------------------------------------- > > Key: PORTAL-42 > URL: http://issues.hippo.nl/browse/PORTAL-42 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > -- 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 Mon Sep 29 15:24:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 15:24:39 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-71) check maven remote repository configuration in getting started docs In-Reply-To: <28988610.1214916064562.JavaMail.root@hat01> Message-ID: <29944363.1222694678221.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-71. ---------------------------------- Resolution: Fixed Improved the portal-demo documentation > 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: Jeroen Hoffman > 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 Mon Sep 29 15:24:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 15:24:40 2008 Subject: [Hippoportal-dev] [JIRA] Resolved: (PORTAL-16) The demo-portal installation & setup instruction should be more elaborate Message-ID: <3880118.1222694678262.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman resolved PORTAL-16. ---------------------------------- Resolution: Fixed Improved the portal-demo documentation > The demo-portal installation & setup instruction should be more elaborate > ------------------------------------------------------------------------- > > Key: PORTAL-16 > URL: http://issues.hippo.nl/browse/PORTAL-16 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > The installation/setup instructions doesn't mention that: > - JDK 1.5 is required for running the portal > - preview.localhost (and live.localhost) should be configured to map to localhost on the installation machine > - For running on Linux, instructions should be given how to set the executable bit on the required shell scripts and how to start both the repository and the portal -- 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 Mon Sep 29 16:12:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 16:12:38 2008 Subject: [Hippoportal-dev] [JIRA] Reopened: (PORTAL-42) Cleanup and improve demo portal setup and configuration In-Reply-To: <3314890.1199369577178.JavaMail.jira@hat01> Message-ID: <19501119.1222697558167.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman reopened PORTAL-42: ---------------------------------- > Cleanup and improve demo portal setup and configuration > ------------------------------------------------------- > > Key: PORTAL-42 > URL: http://issues.hippo.nl/browse/PORTAL-42 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > -- 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 Mon Sep 29 17:15:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 17:15:37 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-42) Cleanup and improve demo portal setup and configuration In-Reply-To: <3314890.1199369577178.JavaMail.jira@hat01> Message-ID: <15042878.1222701338119.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen Hoffman closed PORTAL-42. -------------------------------- Resolution: Fixed link to 1.07 installer added release notes > Cleanup and improve demo portal setup and configuration > ------------------------------------------------------- > > Key: PORTAL-42 > URL: http://issues.hippo.nl/browse/PORTAL-42 > Project: Hippo Portal > Issue Type: Improvement > Components: demo-portal > Affects Versions: 1.06.00 > Reporter: Ate Douma > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > -- 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 Mon Sep 29 17:18:38 2008 From: helpdesk at hippo.nl (JIRA (Dennis Dam)) Date: Mon Sep 29 17:18:38 2008 Subject: [Hippoportal-dev] [JIRA] Closed: (PORTAL-55) Upgrade to snapshot build of Jetspeed-2.1.3-postrelease to synchronize with 2.1.3-postrelease fixes and enhancements In-Reply-To: <9490412.1210935466775.JavaMail.jira@hat01> Message-ID: <10668613.1222701518144.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Dam closed PORTAL-55. ---------------------------- Assignee: Dennis Dam (was: Ate Douma) Resolution: Fixed upgraded to latest unchanged revision of the Jetspeed-2.1.3-POSTRELEASE branch (revision 693323). The Jetspeed dependencies (*-r693323.jar) are available from the public Maven repository at http://repository.hippocms.org/maven. > Upgrade to snapshot build of Jetspeed-2.1.3-postrelease to synchronize with 2.1.3-postrelease fixes and enhancements > -------------------------------------------------------------------------------------------------------------------- > > Key: PORTAL-55 > URL: http://issues.hippo.nl/browse/PORTAL-55 > Project: Hippo Portal > Issue Type: Bug > Affects Versions: 1.07.00 > Reporter: Ate Douma > Assignee: Dennis Dam > Fix For: 1.07.00 > > > There are several enhancements and fixed for Jetspeed-2.1.3 in its 2.1.3-postrelease branch. > Although these have not been formally released yet, Hippo Portal needs some of these fixes. > Examples: > https://issues.apache.org/jira/browse/JS2-867: Optional portlet session caching of layout view templates > https://issues.apache.org/jira/browse/JS2-812: Better support for MSSQL > We will provide snapshot builds of the jetspeed-2.1.3-postrelease branch through our Hippo Maven 1 remote repository: http://repository.hippocms.org/maven > Make sure to have that repository added on your maven.repo.remote property in the build.properties (or project.properties if not using build.properties) > First snapshot build (with fixes for JS2-867 and part of JS2-812) will be against the Apache svn revision r656971. > The Hippo Portal components and artifacts dependencies will be updated to depend on this build, e.g. like -2.1.3-r656971.jar > This issue will be kept open until the release of Hippo Portal 1.0.7 or a newer formal release of Jetspeed becomes available before that. -- 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 Mon Sep 29 17:40:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 17:40:37 2008 Subject: [Hippoportal-dev] [JIRA] Created: (PORTAL-84) Finalize release 1.07 Message-ID: <29876163.1222702838284.JavaMail.jira@hat01> Finalize release 1.07 --------------------- Key: PORTAL-84 URL: http://issues.hippo.nl/browse/PORTAL-84 Project: Hippo Portal Issue Type: Task Components: demo-pa, demo-portal, demo-portal-installer, hippo-portal, hippo-portal-api, hippo-portal-docs, hippo-portal-j2, hippo-portal-maven-plugin, hippo-portal-pac Reporter: Jeroen Hoffman Assignee: Jeroen Hoffman Fix For: 1.07.00 - set version number in trunk to 1.07.00 - create installer for demo - set the tag - upload doc and artifacts to maven repository - more? -- 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 Mon Sep 29 21:42:38 2008 From: helpdesk at hippo.nl (JIRA (Jeroen Hoffman)) Date: Mon Sep 29 21:42:37 2008 Subject: [Hippoportal-dev] [JIRA] Commented: (PORTAL-84) Finalize release 1.07 In-Reply-To: <29876163.1222702838284.JavaMail.jira@hat01> Message-ID: <10192800.1222717358104.JavaMail.jira@hat01> [ http://issues.hippo.nl/browse/PORTAL-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39103 ] Jeroen Hoffman commented on PORTAL-84: -------------------------------------- Tagged and released. Yet, to do: - create installer for demo - create link portal.hippocms.org to the documentation > Finalize release 1.07 > --------------------- > > Key: PORTAL-84 > URL: http://issues.hippo.nl/browse/PORTAL-84 > Project: Hippo Portal > Issue Type: Task > Components: demo-pa, demo-portal, demo-portal-installer, hippo-portal, hippo-portal-api, hippo-portal-docs, hippo-portal-j2, hippo-portal-maven-plugin, hippo-portal-pac > Reporter: Jeroen Hoffman > Assignee: Jeroen Hoffman > Fix For: 1.07.00 > > > - set version number in trunk to 1.07.00 > - create installer for demo > - set the tag > - upload doc and artifacts to maven repository > - more? -- 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 a.douma at onehippo.com Mon Sep 29 22:14:52 2008 From: a.douma at onehippo.com (Ate Douma) Date: Mon Sep 29 22:14:52 2008 Subject: [Hippoportal-dev] [ANNOUNCEMENT] Hippo Portal 1.07.00 released Message-ID: <48E1373C.3050004@onehippo.com> Hippo is proud to announce the availability of the latest release of its Hippo Portal product, version 1.07.00. This new version provides many improvements and enhancements developed over almost a year, and is to a large extend based on the many requests and feedback we got from our community and our partners. For this, we'll like to express our sincere thanks, and are looking forward to continued collaboration on further improving and expanding the usage of Hippo Portal. The new release artifacts are all available through our public Maven-1 repository at: http://repository.hippocms.org/maven/nl.hippo.portal/. The online project documentation is also provided through that location: http://repository.hippocms.org/maven/nl.hippo.portal/docs/hippo-portal-1.07.00/ Finally, the release notes highlighting the new features, improvements and bugs fixed can be found here: http://repository.hippocms.org/maven/nl.hippo.portal/docs/hippo-portal-1.07.00/release-notes.html General usage and getting started information is available at: http://www.hippoportal.org/ The Hippo Portal team -- a.douma@onehippo.com www.onehippo.com Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466 San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA 94952-3329 +1(877) 41-HIPPO