Folks,
I noticed in our DSpace 5.3 trials that a Java exception was being thrown
whenever I tried to access any link which includes /admin/epeople.
Essentially, the resource isn't found.
I ran a number of upgrade tests and discovered that the table "eperson"
remained intact after a DSpace deploy ("ant update"), but once Tomcat was
started and DSpace 5.3 invoked the database migration script, my table for
"eperson" changed in the following manner:
DSpace 4.3 table "eperson":
eperson_id,email,password,firstname,lastname,can_log_in,require_certificate,self_registered,last_active,sub_frequency,phone,netid,language,salt,digest_algorithm
DSpace 5.3 table "eperson" after a migration from 4.3:
eperson_id,email,password,can_log_in,require_certificate,self_registered,last_active,sub_frequency,netid,salt,digest_algorithm
Of note, the name, language, and phone columns have disappeared. I've noticed
some other substantial changes in other tables which might or might not be
affected in the same way, but in this case I can absolutely confirm that
something is errant.
Other than the Java exception, I can't create a new administrator on the
command line since that process can't find the name fields to populate.
I have not yet found anything incriminating in the log files related to the
migration process.
Here's the Java exception for reference:
http://pastebin.com/wfAKbGqe
-Jeff
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
