-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
JWS 5.0.0 GA
-
None
The QE test suite found that this issue was not fixed in JWS 3.1. This is because the tomcat-vault version used in 3.1.0 (there have been no updates as of 3.1.7) was 1.0.8.Final.
This is not a security issue, so unless a customer is requesting it we should reject it.
- clones
-
JWS-1403 Update all of the StringManager references back to the original class reference and add the call to getPackage().getName() so that the inits are able to find LocalStrings.properties in the correct packages
- Closed