Connector core repository updated.

example/checksum-loader.rst

@@ -3,7 +3,7 @@ Checksum loader
 
 Many shop systems (endpoints) have the ability to work with product variation combinations.
 Usually, due to its complex data structure, this is one of the most heavyweight and resource intensive tasks.
-To avoid unnecessary database queries and/or file operations, and to guarantee optimal performance the JTL-Connector uses an object of the interface `jtl\\Connector\\Checksum\\IChecksumLoader <https://github.com/jtl-software/connector/blob/2.6/src/Checksum/IChecksumLoader.php>`_.
+To avoid unnecessary database queries and/or file operations, and to guarantee optimal performance the JTL-Connector uses an object of the interface `jtl\\Connector\\Checksum\\IChecksumLoader <https://github.com/jtl-software/connector-core/blob/2.6/src/Checksum/IChecksumLoader.php>`_.
 
 It provides methods to write, read and delete checksums based on an endpoint id and its corresponding data type (for now we only use it for products).
 

example/primary-key-mapper.rst

@@ -7,7 +7,7 @@ A key component in every endpoint is the **primary key mapper**.
 This special class translates between JTL-Wawi's information and the shop's database.
 It identifies each object by its *database primary key* (PK) and stores mapping information that represent the relation between JTL-Wawi's PK (called **host ID**) and the PK used in the shop (called **endpoint ID**).
 
-All primary key mapper classes implement the interface `jtl\\Connector\\Mapper\\IPrimaryKeyMapper <https://github.com/jtl-software/connector/blob/2.6/src/Mapper/IPrimaryKeyMapper.php>`_.
+All primary key mapper classes implement the interface `jtl\\Connector\\Mapper\\IPrimaryKeyMapper <https://github.com/jtl-software/connector-core/blob/2.6/src/Mapper/IPrimaryKeyMapper.php>`_.
 This interface enforces simple CRUD operations on all available mappings.
 It is up to the endpoint to decide how these mappings are stored providing that they are somehow persistent.
 

example/token-loader.rst

@@ -6,7 +6,7 @@ Token loader
 JTL-Connector uses an **authorization token** to authenticate clients and authorize access to the endpoint.
 This token is entered as synchronization password inside JTL-Wawi.
 As JTL-Connector strives to be as flexible as possible it does not enforce a certain procedure on how to store this password.
-It thus delegates this task to the endpoint, communicating via an object of interface `jtl\\Connector\\Authentication\\ITokenLoader <https://github.com/jtl-software/connector/blob/2.6/src/Authentication/ITokenLoader.php>`_.
+It thus delegates this task to the endpoint, communicating via an object of interface `jtl\\Connector\\Authentication\\ITokenLoader <https://github.com/jtl-software/connector-core/blob/2.6/src/Authentication/ITokenLoader.php>`_.
 
 This interface has only one method :code:`load()` that returns the correct auth token for the endpoint.
 

glossary/jtlconnector.rst

@@ -7,4 +7,4 @@ jtlconnector
 The official implementation of the protocol used by JTL-Connector and JTL-Wawi.
 You are free to use this library in your endpoint implementations and if they are written in the PHP programming language its use is strongly recommended to stay compatible with future versions of JTL-Wawi.
 
-The source code is available on `GitHub <https://github.com/jtl-software/connector>`_
+The source code is available on `GitHub <https://github.com/jtl-software/connector-core>`_