1

I upgraded to DSpace 5.0 from 4.2. I installed DSpace 5.0 freshly. That is, I created a new database and a new installation folder before building and deploying. In the [dspace-source]/build.properties, I specified jspui as my user interface. After installation I'm unable to access jspui from the browser, whereas the xmlui is working perfectly. The jspui comes up as a blank page.

Could someone help me out. Thanks in advance

Here is my dspace error log.

Poonam Anthony
  • 1,848
  • 3
  • 17
  • 27
  • 2
    Try looking for errors in your dspace.log, it would help you figure out what's wrong why jspui comes up as a blank page. – euler Apr 22 '15 at 14:07
  • @euler I've added a link to the error log. the error says `org.apache.jasper.JasperException: Unable to compile class for JSP:`. Please check. – Poonam Anthony Apr 23 '15 at 04:34

2 Answers2

1

In my case, when I encountered that error, I replaced all instances of <artifactId>servlet-api</artifactId> with <artifactId>javax.servlet-api</artifactId> to all the pom.xml files as stated here: install error for upstream/master and here

Also try to delete or remove the 

    <dependency>
        <groupId>com.google.oauth-client</groupId>
        <artifactId>google-oauth-client-jetty</artifactId>
    </dependency>

from dspace-api.pom.xml and do an mvn clean after changing the pom.xml files.

Hope this helps.

euler
  • 1,401
  • 2
  • 18
  • 39
  • I did the same, had to change a bunch of pom.xml files. I also changed my servlet-api version to 3.1.0. Did an mvn clean package and ant update, and voila! I got my jspui interface. This was such a tedious solution. Is there no better way? Will moving to a lower version of tomcat help? – Poonam Anthony Apr 23 '15 at 10:23
  • @PoonamAnthony, yes it was such a tedious solution if you're not using an IDE. If you're using an IDE like Intellij, it would make your coding easier. I did not encounter that error in our production server which is using tomcat 7, but sooner or later, we would have to upgrade to tomcat 8 if it is really required. – euler Apr 23 '15 at 10:57
  • Thanks, I'll import my dspace code into an IDE. This problem had me scratching my head for the last 3 days, until I finally found a solution to it today. – Poonam Anthony Apr 23 '15 at 12:05
  • Thanks @euler, I thought I'd seen this before somewhere! – schweerelos Apr 23 '15 at 21:18
0

According to your log file, you're using Tomcat 8. Other people are reporting similar problems with Tomcat 8 (not with DSpace though): getDispatcherType() is undefined for the type HttpServletRequest and Tomcat 8 giving JSP compilation error

DSpace 5 is supposed to work with Tomcat 8 -- the installation instructions say "Tomcat 7 or later": https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace#InstallingDSpace-ServletEngine(ApacheTomcat7orlater,Jetty,CauchoResinorequivalent)

You say you were using Tomcat 8 with DSpace 4.2 already, so this probably isn't it. Can you confirm that you ran maven with the "clean" target?

mvn clean package

Community
  • 1
  • 1
schweerelos
  • 2,189
  • 2
  • 17
  • 25
  • yes I was using Tomcat 8.0.17 with dspace 4.2. I came across the same problem being reported [Here](http://sourceforge.net/p/dspace/mailman/message/33532346/). But the solution is not very clear to me. – Poonam Anthony Apr 23 '15 at 06:31
  • 1
    I just saw that you said you created a new installation folder, so the mvn clean may not do too much. This is starting to sound like a DSpace bug, so you may wish to report this on the official DSpace bug tracker: https://jira.duraspace.org/browse/DS/ – schweerelos Apr 24 '15 at 05:04