On Thu, Apr 02, 2009 at 07:10:15AM +0700, Panyarak Ngamsritragul wrote: > In the process of 'mvn package', there is a warning: > [WARNING] The following patterns were never triggered in this artifact > exclusion filter: o '*:war:*'
I always see that too. It seems to be something we can ignore. > It reported finally that the process was successful. > > Running 'ant fresh_install' was also successful. > > I created dspace.xml containing > > <Context path="/dspace" > docBase="/dspace/webapps/jspui" debug="0" > reloadable="true" AllowLinking="true" > CachingAllowed="false"/> The 'path' attribute should only be used when the Context is defined in server.xml -- which should not be done. When a Context is defined in a separate file, the name of the file (minus '.xml') determines the path. So, naming the file 'dspace.xml' has already specified that the context path will be '/dspace'. > in /etc/tomcat6/Catalina/localhost and then restart tomcat6. > When I read the tomcat6's log file, it contains warnings and errors like: > > Apr 1, 2009 10:37:15 PM org.apache.catalina.users.MemoryUserDatabase save > WARNING: User database is not persistable - no write permissions on directory That should not be a problem. I consider it a bug in Tomcat that it wants to open that file read-write. It is complaining that tomcat-users.xml is read-only for user 'tomcat'. This should not affect your application. > Apr 1, 2009 10:37:16 PM org.apache.catalina.core.StandardContext processTlds > SEVERE: Error reading tld listeners javax.servlet.ServletException: Exception > processing TLD at resource path /WEB-INF/fmt.tld in context /dspace > javax.servlet.ServletException: Exception processing TLD at resource path > /WEB-INF/fmt.tld in context /dspace [backtrace] > Caused by: java.security.AccessControlException: access denied > (java.io.FilePermission /usr/share/java/jsp-api-2.1.jar read) > at > java.security.AccessControlContext.checkPermission(AccessControlContext.java:342) > at > java.security.AccessController.checkPermission(AccessController.java:553) > at java.lang.SecurityManager.checkPermission(SecurityManager.java:549) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at java.util.zip.ZipFile.<init>(ZipFile.java:126) > at java.util.jar.JarFile.<init>(JarFile.java:150) > at java.util.jar.JarFile.<init>(JarFile.java:87) [etc.] That's your problem: access to jsp-api-1.2.jar denied. You later posted some 'ls' output which indicates that the file should be readable. I'm not very familiar with the SecurityManager, but seeing it in the call stack suggests that your Java environment has been configured to forbid fetching JARs from that path. There's something about this that doesn't look to me like an ordinary filesystem access problem. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Friends don't let friends publish revisable-form documents.
pgp5V38rFQmJ7.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
