IntroductionThis article will solely focus on the building blocks that are unique to eccenca. For details of SMILA see its Architecture Overview. Interaction with eccencaThe unique eccenca parts are controlled and triggered by messages conveying the command or task that they represent. These messages are in general synchronous and hence they do not form a message driven system, as is more the case for SMILA. However, the messages have been designed in XML for which well defined schemas exist. These schemas are contained in either the /xml folder or the respective bundle that defines them. All interaction with the eccenca parts of the framework occur with these messages which can be converted to and from an object graph (look for respective S<message name>Codec) that is much easier to work with programmatically.
|