After the 0.9.2 upgrade, the KEW Document Search page throws an error instead of rendering. There is some more background below, but after commenting out the offending keys in the DocumentSearch.jsp and getting the page to come up, what looks to be happening is that we're getting properties for the doc search labels from KEN's ApplicationResources.properties file instead of from KEW's ApplicationResources.properties file. Is this a bug, or a misconfiguration on our part?
-------- Original Message --------
Subject: Re: Rice 0.9.2
Date: Wed, 17 Oct 2007 16:42:36 -0400
From: Bryan G. Hutchinson <email@example.com>
To: McGregor, Geoffrey Garrett <gmcgrego@INDIANA.EDU>
References: <F99B6AC4E57EAB4092053EFCC81FF87901F0E092@iu-mssg-mbx102.ads.iu.edu> <47166D95.firstname.lastname@example.org>
This one is odd. I see that key in the ApplicationResources.properties
that is in kew/src/main/resources/edu.iu.uis.eden in the Rice 0.9.2
project, and I see the same file in our rice-kew-0.9.2-SNAPSHOT.jar in
our KRA Maven2 Dependencies. So why do you suppose the JSP can't find it?
Bryan G. Hutchinson wrote:
> Here's another post 0.9.2 bug. It looks like we're missing the
> ApplicationResources.properties for KEW. When navigating to the doc
> search through our KRA Portal, Geo noticed the following error:
> HTTP ERROR: 500
> Missing message for key
> Caused by:
> javax.servlet.jsp.JspException: Missing message for key
> at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
> I looked in the 0.9.2 source, and that entry is in the
> ApplicationResources.properties that is part of kew, but I'm not sure
> how we get it. Could this be something else that needs to be copied
> over to our project?