axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From axis-...@ws.apache.org
Subject [jira] Closed: (AXIS-1470) Axis client will fail with strict security policy
Date Thu, 22 Jul 2004 02:40:40 GMT
Message:

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Wed, 21 Jul 2004 7:40 PM

Fixed.

Thanks,
dims
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1470

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1470
    Summary: Axis client will fail with strict security policy
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis
 Components: 
             Basic Architecture
   Versions:
             current (nightly)

   Assignee: Davanum Srinivas
   Reporter: Mike Traum

    Created: Wed, 21 Jul 2004 4:59 PM
    Updated: Wed, 21 Jul 2004 7:40 PM
Environment: Linux

Description:
Currennly, attempting to open a client connection using axis will fail under a strict security
policy. FileProvider.check attempts to see if the client-config.wsdd is writable by calling
canWrite(). This will throw a SecurityException if it is not allowed by the security manager,
but this Exception is not caught. I have seen solutions posted to the list stating that the
policy must be changed, but I am running this under Tomcat in a shared hosting environment
so this is not possible.

Here's a patch against the cvs version which I have running successfully in production.


Index: FileProvider.java
===================================================================
RCS file: /home/cvspublic/ws-axis/java/src/org/apache/axis/configuration/FileProvider.java,v
retrieving revision 1.51
diff -u -r1.51 FileProvider.java
--- FileProvider.java	25 May 2004 19:41:43 -0000	1.51
+++ FileProvider.java	21 Jul 2004 23:57:24 -0000
@@ -107,7 +107,13 @@
      * or not the file is read-only.
      */
     private void check() {
-        readOnly = configFile.canRead() & !configFile.canWrite();
+    	try {
+            readOnly = configFile.canRead() & !configFile.canWrite();
+    	}
+    	catch (SecurityException e) {
+    		readOnly = true;
+    	}
+
 
         /*
          * If file is read-only, log informational message



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message