This is a best practices/architecture question . There are many advantages to wraping a web dynpros application's model in a separate Web Dynpro component residing in a separate DC. This creates a clean separation of model from the UI Components, however I would like to confirm if this is really optimal where one of the models is Adaptive RFC. The context nodes of the component controller would be model nodes which means that the element collection is really just a proxy to the model objetcts. To make use of this separate WD Model Comp the context would then be exposed thru the Component Controller instance. This would than be mapped to the using WD component namely the component controller context of the UI Component. And there would be third mapping from the View(s) Context to the UI Component Controller context. I am not convinced this is the best thing to do. It seems like the View Context is mapped to a mapping origin (UI Component Controllers Context) which is pointing to another mapping origin (Model WD Comp Interface Controller) which is just a proxy to the model node and may even get mapped again if the Component Controller of the model is mapping origin for the WD Comp Interface controller. Is it better for each UI WD Component assuming multiple UI WD Components to hold their own adaptive RFC Model reference? This is an architecture question.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.