| RE: [riena-dev] riena.navigation.assemblies |
|
Hi,
The use case for an assembly reference is to define an assembly in one place and use it in different other locations. Specifying an autostart sequence does not make to much sense, as the exact place
within the parent assembly is determined by the position of the assembly ref. The nodes of the assembly ref are created as if they where defined in place of the assembly ref.
Without the assembly reference you would need to duplicate the definition.
This is a static scenario - if you need to create the nodes dynamically you cannot use the assembly refernece.
You also should be aware that when using an assembly reference you'll add dependencies to the parent assembly resulting in a tighter coupling of your application parts, witch may not be desired.
cheers,
-Holger
From: riena-dev-bounces@xxxxxxxxxxx [riena-dev-bounces@xxxxxxxxxxx] On Behalf Of ekke [ekke@xxxxxxxxxxxxxxxx] Sent: Wednesday, August 26, 2009 23:57 To: Riena Developers list Subject: Re: [riena-dev] riena.navigation.assemblies ekke schrieb:
Christian Campo schrieb:but on the other side....the javadoc of the value that is used for reading it INavigationAssemblyExtensionthx - this makes sense because all other attributes must be null, then the assembly is always bound to the same parent (application || subapplication) with same autostart-sequence so at the moment the use-case isn't really clear for me ekke --
ekke (ekkehard gentz) |