This page contains adhoc TODO ideas or topics being currently investigated. Please feel free to comment on these or suggest new ones.
Possibly use the memento design pattern with deserialization. An inner class performs input validation using 'safe' objects, for example, {{long}} to store {{int}} vals and then updates the state of the actual outer class and so on..., Item 50 \[Daconta 03\] |
-Do not serialize keys, certificates or the classes that contain their instances, as deserialization may fail if the same security provider is not present at the remote end. Instead, override the readObject, writeObject methods and encode the data. \[P 202 Oaks 01\] *(unsure if this can be classified as a security error)*- (done) |
Use HttpSession carefully, Item 25 \[Daconta 03\] |
For good portability, do not make the assumption - all DBMSs can tolerate several open ResultSet Objects at a time, Item 41 \[Daconta 03\] |
Error
(done)Use a typesafe enum pattern \[Bloch, Item 20\]- (_enum type_ provided, jdk 1.5 onwards, [Docs|http://java.sun.com/j2se/1.5.0/docs/guide/language/enums.html]) |
compareTo()
contract violations like natural ordering that is not consistent with equals
(done)Usage of {{GetResource}} may be unsafe if class is extended \[Findbugs\] |
SignedObject
should be first, followed by SealedObject
) (done)