Thanks, Bill, I've made the same change. Hate to commit something like that to 
my local SVN, so just made it in the live code while I try to debug further.
 
Anyone else notice this problem with 1.5.1? Claudia mentioned that this issue 
had been fixed in the 1.5.x branch, but I don't see any signs of that, but I'm 
sure I'm just looking in the wrong places.
 
I've also seen some recent messages that mention a patch queue? Can someone 
point me to more info on that? Thanks!
 
--
HARDY POTTINGER <[EMAIL PROTECTED]>
University of Missouri Library Systems
http://lso.umsystem.edu/~hardy/

________________________________

From: Anderson, Charles W [mailto:[EMAIL PROTECTED]
Sent: Fri 10/17/2008 10:09 AM
To: Pottinger, Hardy J.
Cc: [email protected]
Subject: Re: [Dspace-tech] DSpace 1.5.1 -- Mysterious new feature?



Yeah, that's the same problem.  We were originally getting a system error
every time we clicked on a collection; we got past this by locating
the constant (it's in org.dspace.app.webui.servlet.MyDSpaceServlet, which IS
imported in the collection-home and community-home jsps, but doesn't
resolve properly) and hardcoding it's value (5) -- obviously not a
permanent solution.  We're now able to view collections, but get a
malformed request error whenever we try to click on the new button.   
I haven't had time to track the problem any further than that, so we just
haven't upgraded in production yet.  If we get any further, I'll let you
know -- let me know if you find anything.

Cheers,

Bill

----- Original Message -----
From: "Hardy J. Pottinger" <[EMAIL PROTECTED]>
To: [email protected]
Sent: Thursday, October 16, 2008 6:45:47 PM GMT -05:00 US/Canada Eastern
Subject: Re: [Dspace-tech] DSpace 1.5.1 -- Mysterious new feature?

Hi, we've also recently upgraded to DSpace 1.5.1 (hoping to see xmlui
work better with Oracle), and are also getting these "Internal System
Error" messages on the jspui side (which we use as an admin interface,
since xmlui doesn't always play nice with Oracle). I'm trying to
implement the change suggested by Claudia Juergen, however, it appears
that dspace-api/src/main/resources/Messages.properties already has the
tags in question. The error appears to result from a missing constant,
namely MyDSpaceServlet.REQUEST_EXPORT_ARCHIVE. I'm now combing through
commit messages in the dspace-1_5_x branch, looking for any related
changes that might be required to get this working. However, if anyone
could point me in the right direction, I'd be much obliged. Thanks!

--
HARDY POTTINGER <[EMAIL PROTECTED]>
University of Missouri Library Systems
http://lso.umsystem.edu/~hardy/
"No matter how far down the wrong road you've gone,
turn back." --Turkish proverb

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

--
Bill Anderson
Software Developer
Digital Library Development
Georgia Tech Library



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to