On 11/22/2010 05:39 PM, Patricia Shanahan wrote:
I think I understand what you are saying, but I'm not 100% sure, so I'm
going to repeat back the message I'm getting:
The implementation of SharedActivationPolicyPermission depends on
FilePermission. Its Javadoc comment requires a policy string argument
that conforms to the FilePermission policy string semantics.
A URL, in general, is not a valid FilePermission policy string. On the
other hand, a File path is. Incidentally, I've tested handling of the
FilePermission wildcards in the File class, and it all works.
File can do the "/" conversion correctly and automatically for the
system on which it is run. Doing the conversion on the file path portion
of the URL makes the test case I've been working on pass on both Windows
and Ubuntu.
Even if we make no change in the actual interface,
SharedActivationPolicyPermission should enforce its stated requirement
that the policy string constructor argument conform to FilePermssion
policy semantics.
Yes! RST 559!
