Sorry to hear you are having these troubles. Could you send us full stack traces from the null pointer exceptions, and the associated URLs that cause these? These will enable us to pinpoint the issue.
IT Innovations Analyst and Developer
Te Tumu Herenga The University of Auckland Library
Auckland Mail Centre, Private Bag 92019, Auckland 1142, New Zealand
Ph: 64 9 373-7599 x81928
http://www.library.auckland.ac.nz <http://www.library.auckland.ac.nz/> /
From: David Marcinkowski [mailto:dmarcink@...]
Sent: Thursday, 23 July 2009 9:47 a.m.
Subject: [Dspace-tech] problems with searching in 1.5.1
I have an installation of dspace 1.5.1 running on freeBSD.
I ran 1.4.1 for a while with few issues ......but when we upgraded the server and installed 1.5.1 we started having issues.
I am able to create communities and upload articles, but when I try to search by community, author, title, subject or issue date I get Internal System errors.
In Manakin, I can do a straight search and it seems to work, by if I try to search by author, or title, etc I get a "java.lang.NullPointerException" error
From: Mark Diggory [mailto:mdiggory@...]
Sent: Wednesday, July 08, 2009 5:44 PM
To: Patrick K. Etienne
Subject: Re: [Dspace-tech] DSpace (Manakin) - entities & link/meta tags
I would highly recommend that the content of these meta tags needs to remain escaped as so to be embedded into an html attribute value properly, otherwise you are violating the html spec.
On Wed, Jul 8, 2009 at 1:09 PM, Patrick K. Etienne <patrick.etienne@...> wrote:
I've been working on a fairly in-depth (Manakin) redesign for a DSpace instance and am having trouble when displaying simple or full item records. On those two page types, additional information is embedded within the "head" section of the html code in the form of "link" and "meta" tags. The "<" and ">" symbols that open and close the link/meta tags are showing up within the source as ">", "<". The source seems to be from the "buildHead" template within the "structural.xsl" stylesheet. Near the bottom of that template is the following code:
<!-- Head metadata in item pages -->
My understanding is that the disable-output-escaping attribute should be preventing this behavior, resolving those entities as the actual symbols rather than representative counterparts. For some reason they are being translated as entities rather than being taken as literals. If anyone has any suggestions, I'd be very much obliged.
- Patrick E.
Patrick K. Étienne
Digital Library Development
Library and Information Center
Georgia Institute of Technology
"Mediocre Writers Borrow; Great Writers Steal" - T.S. Eliot
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
DSpace-tech mailing list