on 07-08-2005 10:57 AM
Hi All,
Earlier we used to create separate dll for each BAPI.. Now we can have multiple Proxy in a single project (ver 2.0). But I am really confused of determining which way I have to adapt for the new development.
Thanks in Advance.
There is no conceptional change from 1.x to 2.x in this area. Also before you could have multiple .sapwsdl files in a project where each can contain multiple methods.
With 2.0 it's just easier, especially for the VB-Developer, because you can now have your proxies directly in your application.
I'd suggest the following rule:
- Inside of a .sapwsdl group the methods that belong together. A special case is the use of a BOR class. In this case NCo would automatically create you a single class that represents the whole BOR class with all BAPI that belong to it.
- For simple projects hold all .sapwsdls directly in your project.
- I you reuse proxies in multiple projects, put them together in a seperate DLL project. This project can also contain any additional shielding and logic that make the DLL a reusable thing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
101 | |
13 | |
13 | |
11 | |
11 | |
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.