Author: rhauch Date: 2010-01-10 11:16:31 -0500 (Sun, 10 Jan 2010) New Revision: 1586 Modified: trunk/docs/reference/src/main/docbook/en-US/content/core/connector.xml Log: Merge branch 'dna-621' Modified: trunk/docs/reference/src/main/docbook/en-US/content/core/connector.xml =================================================================== --- trunk/docs/reference/src/main/docbook/en-US/content/core/connector.xml 2010-01-10 16:13:40 UTC (rev 1585) +++ trunk/docs/reference/src/main/docbook/en-US/content/core/connector.xml 2010-01-10 16:16:31 UTC (rev 1586) @@ -238,12 +238,12 @@ UUID or other identifier), consider implementing &MapRepositorySource;, subclassing &MapRepository;, and using the existing &MapRepositoryConnection; implementation. This &MapRepositoryConnection; does most of the work already, relying upon your &MapRepository; subclass for anything that might be source-specific. - (See the <ulink url="&API;graph/connector/map/package-frame.html">JavaDoc</ulink> for details.) + (See the <ulink url="&API;graph/connector/map/package-summary.html">JavaDoc</ulink> for details.) Or, if the content your connector exposes is simply path-based, consider implementing &PathRepositorySource;, subclassing &PathRepository;, and using the existing &PathRepositoryConnection; implementation. Again, &PathRepositoryConnection; class does almost all of the work and delegates to your &PathRepository; subclass for anything that might be source-specific. - (See the <ulink url="&API;graph/connector/path/package-frame.html">JavaDoc</ulink> for details.) + (See the <ulink url="&API;graph/connector/path/package-summary.html">JavaDoc</ulink> for details.) </para> <para> Don't forget unit tests that verify that the connector is doing what it's expected to do. (If you'll be committing the connector