ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 1161] New - wlrun doesn't allow setting java.security.policy file outside of weblogic.system.home
Date Fri, 30 Mar 2001 19:11:34 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1161

*** shadow/1161	Fri Mar 30 11:11:33 2001
--- shadow/1161.tmp.16950	Fri Mar 30 11:11:33 2001
***************
*** 0 ****
--- 1,37 ----
+ +============================================================================+
+ | wlrun doesn't allow setting java.security.policy file outside of weblogic. |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 1161                        Product: Ant                     |
+ |       Status: NEW                         Version: 1.3                     |
+ |   Resolution:                            Platform: PC                      |
+ |     Severity: Normal                   OS/Version: Windows NT/2K           |
+ |     Priority:                           Component: Optional Tasks          |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: ant-dev@jakarta.apache.org                                   |
+ |  Reported By: johnson@pilot.msu.edu                                        |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ The WLRun task's policy attribute assumes the attribute value is a path 
+ relative to the weblogic.system.home directory, although all it does is set the 
+ java.security.policy System property, and that property has no such 
+ restriction.  
+ 
+ In 1.2, I could get around this restriction and use a policy file located 
+ elsewhere by setting java.security.policy directly as part of the jvmargs 
+ attribute instead of using the policy attribute.
+ 
+ In 1.3, the java.security.policy (and all other jvm args that are set by 
+ attributes) are blindly appended to the jvm args set directly using the jvmargs 
+ attribute, so I can no longer reference a policy file outside of 
+ weblogic.system.home, because my setting gets overridden by the later incorrect 
+ (default) setting.
+ 
+ 1.  WLRun should allow for the value of the policy attribute to be a complete 
+ path, not just one relative to the weblogic.system.home.
+ 2.  WLRun should put attribute-based jvm args BEFORE those directly set with 
+ the jvmargs.
+ 
+ (I am using WebLogic 5.1)

Mime
View raw message