--- old/src/java.naming/share/classes/javax/naming/spi/StateFactory.java 2015-08-04 13:15:13.708901265 +0300 +++ new/src/java.naming/share/classes/javax/naming/spi/StateFactory.java 2015-08-04 13:15:13.384901258 +0300 @@ -34,14 +34,14 @@ * The JNDI framework allows for object implementations to * be loaded in dynamically via object factories. * For example, when looking up a printer bound in the name space, - * if the print service binds printer names to References, the printer - * Reference could be used to create a printer object, so that + * if the print service binds printer names to {@code Reference}s, the printer + * {@code Reference} could be used to create a printer object, so that * the caller of lookup can directly operate on the printer object * after the lookup. - *

An ObjectFactory is responsible + *

An {@code ObjectFactory} is responsible * for creating objects of a specific type. In the above example, - * you may have a PrinterObjectFactory for creating - * Printer objects. + * you may have a {@code PrinterObjectFactory} for creating + * {@code Printer} objects. *

* For the reverse process, when an object is bound into the namespace, * JNDI provides state factories. @@ -50,23 +50,23 @@ *

   * ctx.rebind("inky", printer);
   * 
- * The service provider for ctx uses a state factory - * to obtain the state of printer for binding into its namespace. - * A state factory for the Printer type object might return + * The service provider for {@code ctx} uses a state factory + * to obtain the state of {@code printer} for binding into its namespace. + * A state factory for the {@code Printer} type object might return * a more compact object for storage in the naming system. *

- * A state factory must implement the StateFactory interface. + * A state factory must implement the {@code StateFactory} interface. * In addition, the factory class must be public and must have a * public constructor that accepts no parameters. *

- * The getStateToBind() method of a state factory may + * The {@code getStateToBind()} method of a state factory may * be invoked multiple times, possibly using different parameters. * The implementation is thread-safe. *

- * StateFactory is intended for use with service providers - * that implement only the Context interface. - * DirStateFactory is intended for use with service providers - * that implement the DirContext interface. + * {@code StateFactory} is intended for use with service providers + * that implement only the {@code Context} interface. + * {@code DirStateFactory} is intended for use with service providers + * that implement the {@code DirContext} interface. * * @author Rosanna Lee * @author Scott Seligman @@ -81,18 +81,18 @@ /** * Retrieves the state of an object for binding. *

- * NamingManager.getStateToBind() + * {@code NamingManager.getStateToBind()} * successively loads in state factories and invokes this method * on them until one produces a non-null answer. - * DirectoryManager.getStateToBind() + * {@code DirectoryManager.getStateToBind()} * successively loads in state factories. If a factory implements - * DirStateFactory, then DirectoryManager - * invokes DirStateFactory.getStateToBind(); otherwise - * it invokes StateFactory.getStateToBind(). + * {@code DirStateFactory}, then {@code DirectoryManager} + * invokes {@code DirStateFactory.getStateToBind()}; otherwise + * it invokes {@code StateFactory.getStateToBind()}. *

When an exception * is thrown by a factory, the exception is passed on to the caller - * of NamingManager.getStateToBind() and - * DirectoryManager.getStateToBind(). + * of {@code NamingManager.getStateToBind()} and + * {@code DirectoryManager.getStateToBind()}. * The search for other factories * that may produce a non-null answer is halted. * A factory should only throw an exception if it is sure that @@ -110,7 +110,7 @@ * against concurrent access, since context implementations are not * guaranteed to be thread-safe. *

- * The name and environment parameters + * The {@code name} and {@code environment} parameters * are owned by the caller. * The implementation will not modify these objects or keep references * to them, although it may keep references to clones or copies.