on 11-03-2011 2:57 AM
Hi All,
We have a requirement to call a 3rd party web service from SAP for which there are 12 - 13 attributes which are constant values and are not going to change. These can be hard coded inside the implementation methods but I do not want to do it. Say after 3 months there is a additional attribute that need to be added then in that case I need not touch the code back.
We can store it Z tables which is one option. I would like to get ideas from experts here in the forum what would you do in this type of a scenario instead of hard coding?
Please post in your feedback from the maintenance perspective across landscapes.
Thanks,
Nagarajan.
Hello Nagarajan,
you can create the constants in the Assistance class or create a separate interface for storing the constant values.
If there is any change in the constant value, then you have to change the class/interface. this can't be avoided.
BR, Saravanan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As you have already hinted , i would consider ztables,constants in Singleton OO class. However i would prefer ztables in this case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.