Molstructure class

Notice that now each of these two classes extends Molstructure class and all common code is removed from them. This result is because the common behaviors are inherited from the common superclass—Molstructure. Also notice that even some logic in the constructor is inherited from the superclass. Now we have achieved some code reuse through inheritance by having a class hierarchy. 

Notice that the new register ) method takes the abstract class Molstructure as input. At compile time, it does not care whether MolfileStructure or SmilesStructure is bound to it when the application runs. At runtime, depending on what concrete type is passed into the register ) method by its caller, CompoundRegistrationService behaves according to the implementation details of MolfileStructrure or SmilesStructure. 

The other instance variables in the Compound class include a Molstructure object, a list of salt structures, a list of parent structures, a String array that contains information about what has been changed or what the problems are in the structure as a result of the chemistry rules checking, and a Compounds tate object representing the current state of the Compound object. The process() method in the Compound object simply delegates the call to its current state object, which knows how to process the Compound object depending on its current state as described above. 

This implementation of Molstructurelnspector uses CheshireManager to apply chemistry rules to inspect molstructures. Take a close look at the executeRule() method, which is the core of the CheshireMolstructure-Inspectorlmpl class. This private method is called by almost all other... 

---