Thank you - that was the solution to the last problem I was having, I moved xmlui up one directory level. Well, actually I created symlinks to ROOT/xmlui and ROOT/jspui from the ROOT level. That feels like a kludge but it worked. I'll have to test to see if anything else needs to move or be symlinked.
I don't think I did anything wrong during the configuration steps, so why would the DSpace installation software put the necessary directories where they aren't accessible? Your post is from over a year ago and I just installed DSpace6, the current release. But to finally get it to work I had to upgrade Tomcat and openJDK to the newest releases and start fresh. So I suspect the installation documentation hasn't quite caught up with the current version of DSpace. On Saturday, January 2, 2016 at 11:53:55 PM UTC-9, a.bollini wrote: > > Hi Mohamed, > you need to move the jspui folder outside the ROOT directory or, > alternatively, move the content of the jspui folder inside the ROOT folder > i.e. one of the following path need to exists > /apache-tomcat-7.0.42/webapps/jspui/WEB-INF > > Or > /apache-tomcat-7.0.42/webapps/ROOT/WEB-INF > > If you go for the second option (preferred) you will be able to reach the > dspace webapp without using the jspui path in the browser > I.e > Xxx.xxx.xxx.xxx:8080/ > > Andrea > > > Inviato dal mio dispositivo Samsung > > > -------- Messaggio originale -------- > Da: Mohamad CHAITOU <[email protected] <javascript:>> > Data: 02/01/2016 22:27 (GMT+01:00) > A: DSpace Technical Support <[email protected] <javascript:>> > Cc: [email protected] <javascript:>, [email protected] <javascript:> > Oggetto: Re: [dspace-tech] HTTP Status 500 - The absolute uri: > http://www.dspace.org/dspace-tags.tld cannot be resolved > > Dear Andrea, > > The file dspace-tags.tld exists well in the WEB-INF directory: > > net@ubuntu:~/apache-tomcat-7.0.42/webapps/ROOT/jspui/WEB-INF$ *ls | grep > tld* > *dspace-tags.tld* > fmt.tld > researcher.tld > stats.tld > > Even though, the error occurs. > > I had no permission issues (I executed all commands using sudo, even > firefox I started it using gksudo) > > Tomcat runs normally. Below is what I get when I start tomcat: > > Jan 02, 2016 1:14:23 PM org.apache.catalina.startup.Catalina load > INFO: Initialization processed in 759 ms > Jan 02, 2016 1:14:24 PM org.apache.catalina.core.StandardService > startInternal > INFO: Starting service Catalina > Jan 02, 2016 1:14:24 PM org.apache.catalina.core.StandardEngine > startInternal > INFO: Starting Servlet Engine: Apache Tomcat/7.0.42 > Jan 02, 2016 1:14:24 PM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deploying web application directory > /home/net/apache-tomcat-7.0.42/webapps/manager > Jan 02, 2016 1:14:41 PM org.apache.catalina.util.SessionIdGenerator > createSecureRandom > INFO: Creation of SecureRandom instance for session ID generation using > [SHA1PRNG] took [17,308] milliseconds. > Jan 02, 2016 1:14:41 PM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deploying web application directory > /home/net/apache-tomcat-7.0.42/webapps/ROOT > Jan 02, 2016 1:14:41 PM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deploying web application directory > /home/net/apache-tomcat-7.0.42/webapps/host-manager > Jan 02, 2016 1:14:42 PM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deploying web application directory > /home/net/apache-tomcat-7.0.42/webapps/examples > Jan 02, 2016 1:14:42 PM org.apache.catalina.startup.HostConfig > deployDirectory > INFO: Deploying web application directory > /home/net/apache-tomcat-7.0.42/webapps/docs > Jan 02, 2016 1:14:42 PM org.apache.coyote.AbstractProtocol start > INFO: Starting ProtocolHandler ["http-bio-8090"] > Jan 02, 2016 1:14:42 PM org.apache.catalina.startup.Catalina start > INFO: Server startup in 18435 ms > > Any clues ? > > Thanks! > > > > On Saturday, January 2, 2016 at 10:25:15 PM UTC+2, a.bollini wrote: >> >> Dear Mohamad, >> the absolute uri that you refer is only for internal reference of the >> application and it doesn't need to exist at all. >> Can you check if additional information are available in the catalina.out >> at the starting of tomcat? A dspace-tags.tld file should be present in the >> unpackaged jspui webapp. >> It could be related to an issue with files permission. >> Hope this help, >> Andrea >> >> >> >> Inviato dal mio dispositivo Samsung >> >> >> -------- Messaggio originale -------- >> Da: Mohamad CHAITOU <[email protected]> >> Data: 02/01/2016 19:49 (GMT+01:00) >> A: DSpace Technical Support <[email protected]> >> Oggetto: [dspace-tech] HTTP Status 500 - The absolute uri: >> http://www.dspace.org/dspace-tags.tld cannot be resolved >> >> Dear All, >> >> I have been struggling since a week to solve this problem without >> success. >> I installed Dspace CRIS (4.x.x) on ubuntu inside a vmware virtual >> machine. Everything has compiled successfully. However, when I try to >> invoke Dspace from tomact it gives me the following error (plz see below). >> It seems that the uri http://www.dspace.org/dspace-tags.tld is not >> active (I tried to open it from browser but i gives HTTP error 404). >> Please find below the error details and the specifications of my >> installation. >> >> >> HTTP Status 500 - The absolute uri: http://www.dspace.org/dspace-tags.tld >> cannot be resolved in either web.xml or the jar files deployed with this >> application >> >> type Exception report >> >> message The absolute uri: http://www.dspace.org/dspace-tags.tld cannot >> be resolved in either web.xml or the jar files deployed with this >> application >> >> description The server encountered an internal error that prevented it >> from fulfilling this request. >> >> exception >> >> org.apache.jasper.JasperException: The absolute uri: >> http://www.dspace.org/dspace-tags.tld cannot be resolved in either >> web.xml or the jar files deployed with this application >> >> org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:56) >> >> org.apache.jasper.compiler.ErrorDispatcher.dispatch(ErrorDispatcher.java:445) >> >> org.apache.jasper.compiler.ErrorDispatcher.jspError(ErrorDispatcher.java:117) >> >> org.apache.jasper.compiler.TagLibraryInfoImpl.generateTLDLocation(TagLibraryInfoImpl.java:311) >> >> org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:152) >> >> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:410) >> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475) >> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1427) >> org.apache.jasper.compiler.Parser.parse(Parser.java:138) >> >> org.apache.jasper.compiler.ParserController.doParse(ParserController.java:242) >> >> org.apache.jasper.compiler.ParserController.parse(ParserController.java:102) >> org.apache.jasper.compiler.Compiler.generateJava(Compiler.java:198) >> org.apache.jasper.compiler.Compiler.compile(Compiler.java:373) >> org.apache.jasper.compiler.Compiler.compile(Compiler.java:353) >> org.apache.jasper.compiler.Compiler.compile(Compiler.java:340) >> >> org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:646) >> >> org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:357) >> >> org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:390) >> org.apache.jasper.servlet.JspServlet.service(JspServlet.java:334) >> javax.servlet.http.HttpServlet.service(HttpServlet.java:728) >> >> note The full stack trace of the root cause is available in the Apache >> Tomcat/7.0.42 logs. >> Apache Tomcat/7.0.42 >> >> Installation specification >> apache-ant-1.8.4 >> apache-maven-3.0.4 >> apache-tomcat-7.0.42 >> psql (PostgreSQL) 9.4.5 >> Oracle JDK 7 (1.7.0_79) >> >> Thanks in advance, >> Mohamad Chaitou >> >> -- >> 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 https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > -- > 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] <javascript:>. > To post to this group, send email to [email protected] > <javascript:>. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
