Tech-edit

You are viewing an old version of this page. View the current version.

Reviewed by Dhruv. Now ready for David's review.

Guidelines
Page: DCL00-J. Prevent class initialization cycles Page: DCL01-J. Do not reuse public identifiers from the Java Standard Library Page: DCL02-J. Do not modify the collection's elements during an enhanced for statement Page: ENV00-J. Do not sign code that performs only unprivileged operations Page: ENV01-J. Place all security-sensitive code in a single JAR and sign and seal it Page: ENV05-J. Do not deploy an application that can be remotely monitored Page: ERR00-J. Do not suppress or ignore checked exceptions Page: ERR01-J. Do not allow exceptions to expose sensitive information Page: ERR03-J. Restore prior object state on method failure Page: ERR04-J. Do not complete abruptly from a finally block Page: ERR06-J. Do not throw undeclared checked exceptions Page: ERR09-J. Do not allow untrusted code to terminate the JVM Page: EXP07-J. Prevent loss of useful data due to weak references Page: FIO05-J. Do not expose buffers or their backing arrays methods to untrusted code Page: FIO06-J. Do not create multiple buffered wrappers on a single byte or character stream

Guidelines

Reviewed by David. Now ready for Robert's review.

Guidelines
Content by label There is no content with the specified labels

Reviewed by Robert. Now ready for Pennie's edit.

Guidelines
Content by label There is no content with the specified labels

Edited by Pennie. Now complete.

Guidelines
Page: CON50-J. Do not assume that declaring a reference volatile guarantees safe publication of the members of the referenced object Page: CON51-J. Do not assume that the sleep(), yield(), or getState() methods provide synchronization semantics Page: CON52-J. Document thread-safety and use annotations where applicable Page: DCL51-J. Do not shadow or obscure identifiers in subscopes Page: DCL52-J. Do not declare more than one variable per declaration Page: DCL53-J. Minimize the scope of variables Page: DCL54-J. Use meaningful symbolic constants to represent literal values in program logic Page: DCL55-J. Properly encode relationships in constant definitions Page: DCL56-J. Do not attach significance to the ordinal associated with an enum Page: DCL57-J. Avoid ambiguous overloading of variable arity methods Page: DCL59-J. Do not apply public final to constants whose value might change in later releases Page: DCL60-J. Avoid cyclic dependencies between packages Page: EXP50-J. Do not confuse abstract object equality with reference equality Page: EXP51-J. Do not perform assignments in conditional expressions Page: EXP52-J. Use braces for the body of an if, for, or while statement

Guidelines

Space shortcuts