I am thinking in putting the bapi's call in an assistance class.
I read the Reginas comments at WDA Best Practice for Coding and I have some doubts.
Due to each WD Component can have only one assistance class, I'd like to put some methods that not access the database in that class too.
I'm worried about the size of that assistance class. I think it will get very big.
What should I do in terms of architecture?
Should I create others classes or others web dynpro components?
Thanks a lot.
Alejandro Bindi replied
That was my previous post explanation...maybe I was not clear enough.
You can't have more than one assistance class defined per component...so, either you use it as a single "access point" to get references to other model classes, or you instance and use those other classes directly from WD. Nothing wrong with that...the assistance class advantage is just that it is instantiated by the framework, but it is fair enough to separate some overly complex logic into several separate classes.
Edited by: Alejandro Bindi on Oct 20, 2008 1:40 PM