I am going to use a 256 bit key for AES encyption and have the policy files that supports the same. But I don't want to install these files manually at jre/lib/security on server(WAS) as it might break some existing application running on the server.
Packaging the unlimited strength policy jars with my EAR(WEB-INF/lib) would require to change the class loader preference to "PARENT_LAST".
I have following questions :
(a) Is changing the class loader preference the best way out of this situation? (b) Is it possible that installing "unlimited strength policy" can effect other application in a negative way.