on 12-03-2008 3:09 PM
Hi all,
I had a dispute with a colleague about passing data between different WDP Development Components. The situation is like this:
Colleague has a SearchWDP (parent) und I have a BrowseWDP (child). After searching for some objects and clicking a hit in the SearchWDP, the corresponding details should be shown in BrowseWDP, via passing a bunch of parameters such as selected item's id, etc.
Now which of the following is the better practice:
- Defining a node in BrowseWDP (child) with isInputParameter set to TRUE, creating a similar node from the same type (simply via ModelBinding, both WDPs are using the same model) in SearchWDP, and defining a mapping between them so that SearchWDP fills the input nodes. From BrowserWDPs perspective, I'd call this Pull method.
or...
- Defining a node in BrowseWDP (child) with isInputParameter set to FALSE, creating a setter method in BrowseWDP Interface Controller for the collection (to be passed as parameters) and calling a wdContext.nodeBlaBla().bind(pInputParameterFromModelType). From BrowserWDPs perspective, I'd call this Push method.
The colleague's argumentation in favor of Push has not convinced me at all and I'd like to ask your opinions. Is there a best practice or recommendation for this scenario? TIA
ps: Any answer will be rewarded.
Hi Cuneyt,
Refer the links below, they are very informative!
http://help.sap.com/saphelp_nw04s/helpdata/en/22/15a441cd47a209e10000000a155106/content.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/67/cc744176cb127de10000000a155106/content.htm
These links are a part of the WebDynpro ABAP documentation, but the concepts are same for WDA and WDJ.
Considering your scenario, I would recommend the first alternative you have mentioned (if you refer the second link its called External Context Mapping), where component controller context node of component A (SearchWDP) is the source for Interface controller context (same name) of component B (BrowseWDP).
Thanks.
Chitrali
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks to all of you, for all the links to External Context Mapping External Mapping was also my preferred method, however, the colleague's method works, too.
But what I really would like to hear from you is your opinion on the subject, namely potential problems with each of these methods. Perhaps you could share some insight from your past experiences.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
you can read also
[http://help.sap.com/saphelp_nw04s/helpdata/en/66/a5384162316532e10000000a1550b0/content.htm]
Regards
Matteo
Edited by: Matteo Fusi on Dec 4, 2008 9:38 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Please refer this link of external context mapping
http://help.sap.com/saphelp_nw04s/helpdata/EN/67/cc744176cb127de10000000a155106/content.htm
Regards'
Ruturaj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
You can use interfaceView to pass the parameters.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.