Hello,
I'm looking at a bug to do with security settings.
Igor Malinin's patch for 16675 [1] included new SecuritySupport
classes in the org.apache.xml.utils package, and I already want to add new
methods to these classes. However, the classes have package
accessibility, and I want to access them from the
org.apache.xalan.processor package.
I believe the originals in the javax.xml packages had package
accessibility, because the implementors didn't want them to become part of
the public API of JAXP. However, we give many things in Xalan-J public
accessibility, even when we consider them to be part of the private API of
Xalan-J, just because of the way we've structured the packages. Is there
any other reason why I shouldn't make org.apache.xml.utils.SecuritySupport
public?
Thanks,
Henry
[1] http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16675
------------------------------------------------------------------
Henry Zongaro Xalan development
IBM SWS Toronto Lab T/L 969-6044; Phone +1 905 413-6044
mailto:[EMAIL PROTECTED]
