Chuck Imperato commented on Sep 14, 2009

Configuring Multiple Instances of Containers Through Namespaces

Actually, the default behavior is NOT to share the same configuration simply because when using the CAE, each time you drag a component out onto the layout, it is assigned a new primary ID. The way to share configurations is to drag a container component out onto the layout and then create a component from that instance by right clicking on it and selecting that option. This will add a new instance of that same primary view id to the pallette and it will share the configuration of the original. This can be useful if you are deploying applications with many instances of the same component and you want them to have the same configuration. You do not need to to modify the new configuration for each instance of the component when assembling the application.

Karsten HW Lehmann commented on Sep 12, 2009

Configuring Multiple Instances of Containers Through Namespaces

Good to have this namespace property. But I would have expected this to be the default behaviour. If a user drags two browser containers into a CA, why would he want them to share the same landmarks and other properties? I guess in most cases he wants to display different websites and have different landmarks in the containers.