When a connection between a client and a server is established via CLConnection objects on either side both of them will create an associated GroupTransfer object which will be used as the underlying means of data transportation between client and server. The GroupTransfer class itself according to the SEMPER architecture uses the Communication Layer's services to build a connection and to deliver data to its destination.
If a connection has finally been established from one
GroupTransfer to its
corresponding partner, both constructors return thus enabling the
objects above to do their final initialisation. Once their constructors return
as well, the SemperClient/SemperServer may invoke the corresponding business
applications passing them the connection objects.
Each Commerce Layer service class derived from
CLServices makes use of the
CLConnection object it gets on invocation by using its GroupTransfer
object's send/receive services to transmit data tree structures created with the
methods of the
GroupTransfer object sends the data to its counterpart the tree
nodes are interpreted and the appropriate methods of the
Statement Block and the
Payment Block are invoked in order e.g. to
retrieve signatures and to sign the transactions (these features are currently being
These classes are currently used/implemented to provide send/receive and
The following passages will provide a short description of the classes:
Commerce Layer. Each CLConnection object creates its own GroupTransfer object to establish a connection between client and server. This object uses the Communication Block's facilities (see also the chapter about the Communication Layer) to finally build up the connection. An exception will be raised in case there is no way to instantiate a connection.
Furthermore, before the first send/receive invocation, a statement session will be built up for the connection to provide the Statement Manager's services for this connection (Encryption, Authentication, Signature).
Once there exists a GroupTransfer object on either side of a connection, Commerce Layer services can use it to exchange transaction data tree structures stored in containers.
Every time a send method is invoked it processes the data tree structure provided in a container by calling the appropriate services according to the node types, e.g. methods of the Statement Manager in case of statement nodes, resp. Payment Manager in case of payment nodes.
The documentation includes an index and a tree depicting the class structure.
All the files generated by javadoc are found via the package index.