Hi Taher , Thanks for the attention.
Its not just a matter of one service. I dunno when again i would face the same with a different service. A glance over the service references suggest that there is use of GenericValue all over the places. I don't mind using SOAP it gets me out of this soup ;-) I know XMLRPC is lightweight and faster. regds mallah. On Fri, Mar 23, 2018 at 2:40 PM, Taher Alkhateeb <slidingfilame...@gmail.com > wrote: > Hi Rajesh, > > Actually If I were you I would avoid SOAP. Maybe that is too complex > and an overkill for your problem. I never liked soap for anything > other than washing hands anyway :) > > I also think there might be multiple issues with the whole design of > this service, why pass a generic value in the first place! > > So anyway, what is a quick solution for you? Well, a very quick one > for example could be to create a new service that takes all the > arguments that "calculateProductPrice" takes but the product is a Map. > Then, you simply convert the Map to a GenericValue, and then pass > everything to "calculateProductPrice" > > The better solution IMO, is to completely refactor this service, > because DAMN, 485 lines of code! It hurts my eyes just to look at that > jumble of code > > On Fri, Mar 23, 2018 at 11:54 AM, Rajesh Mallah <mallah.raj...@gmail.com> > wrote: > > Hi Jacques , > > Thanks for the reply . > > > > I have almost hit the wall with this current issue :-( > > > > Do you mean to say it may work if i use SOAP ? > > > > > > regds > > mallah. > > > > > > On Fri, Mar 23, 2018 at 2:13 PM, Jacques Le Roux < > > jacques.le.r...@les7arts.com> wrote: > > > >> Le 23/03/2018 à 05:00, Rajesh Mallah a écrit : > >> > >>> I guess we need a procedure to convert incoming > >>> map (or nested maps) to OFBiz genericvalue. > >>> > >> That's SOAP ;) > >> > >> Jacques > >> > >> >
