This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "ESAPI-JavaStatus"
From OWASP
m |
m (→ESAPI 2.0 Release issues) |
||
| Line 1: | Line 1: | ||
== ESAPI 2.0 Release issues == | == ESAPI 2.0 Release issues == | ||
| − | |||
* Augment the Encoder | * Augment the Encoder | ||
** new naming convention | ** new naming convention | ||
| Line 8: | Line 7: | ||
* Ensure all units tests run successfully for Windows+Linux via Java 1.5.0_22 | * Ensure all units tests run successfully for Windows+Linux via Java 1.5.0_22 | ||
* Split Swingset into 1.4 and 2.0 SwingSet | * Split Swingset into 1.4 and 2.0 SwingSet | ||
| + | * Other issues tracked via Google Code [http://code.google.com/p/owasp-esapi-java/issues/list here] | ||
== ESAPI 1.4 Release issues == | == ESAPI 1.4 Release issues == | ||
* Upgrade 1.4 Maven configuration | * Upgrade 1.4 Maven configuration | ||
* Fix Oracle encoder | * Fix Oracle encoder | ||
Revision as of 11:24, 28 November 2009
ESAPI 2.0 Release issues
- Augment the Encoder
- new naming convention
- new fine grained url encoding functions
- DOM XSS encoding functions
- Ensure all units tests run successfully for Windows+Linux via Java 1.5.0_22
- Split Swingset into 1.4 and 2.0 SwingSet
- Other issues tracked via Google Code here
ESAPI 1.4 Release issues
- Upgrade 1.4 Maven configuration
- Fix Oracle encoder
