Articles

This section contains an unsorted set of articles on miscellaneous themes regarding the Chaplin ACT.

• EmitterProxy - This article explains how a proxy can be created for emitting messages into a composite. It may be useful in situations when a method invocation should be distributed to more components in one call. Another usage is making a facade whose interface contains a selection of methods from various services contained in the composite. Read more...

• AttachingMetadata - Since the version 0.4.1 it is possible to attach an arbitrary metadata to every DomainObject?. For accessing the object's metadata the Chaplin ACT enhances every domain class by org.chaplin.Meta interface and its implementation. Read more...

• InstantiatingAbstractClasses - If your component needs to interact with another component you express this need by declaring an abstract method in the component's class. The Chaplin ACT replaces this abstract method with a code emitting a message. As the source component's class is abstract it is not possible to instantiate it with the help of the new operator. As a workaround you can use the $ operator for creating instances from abstract classes. Read more...

• LabelingComponents - You can attach a unique label to any component in a composite. This label assigns a role which the component plays in the composite. Through this label one component can address another one when it needs an interaction within the composite context. Read more...

• AdvancedInteractionBetweenComponents - In this example I show how components may interact in more complex way. It is demonstrated how a context value can be delivered to a component according to the component's role. Furthermore, it is explained how to give components different values of one context field according to the roles of the referencing components. Read more...

• MessageRoutingInComposite - This article explains how messages are processed and routed internally in Chaplin ACT. Read more...