Your class diagrams look dynamite. Thanks for the update. Have a great weekend. Lewis
On Friday, June 19, 2015, Radu Manole <[email protected]> wrote: > Hi, > I uploaded UML diagrams for the rest of the classes. > The predominant similarities are: > - In most cases, the client doesn’t have a additional logic from its > ability to remotely call methods, and where it is it can be separated. > - classes share a lot of similarities that they can be abstracted using > the same similar method used in catalog module creating objects using > factory. > Thanks. > > 2015-06-17 0:05 GMT+03:00 Lewis John Mcgibbney <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>>: > >> Hi Radu, >> >> On Tue, Jun 16, 2015 at 1:42 PM, Radu Manole <[email protected] >> <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: >> >>> >>> I tried adding a UML diagram on the wiki >>> https://cwiki.apache.org/confluence/display/OODT/XMLRPC+uses >>> Although I didn't generate it, but created it by hand. >>> Any feedback is appreciated. >>> >> >> I've formatted and added feedback on there. Nice work. >> >> >>> >>> I can see some similarities in the uses, but I didn't yet write a >>> proposal for separating XMLRPC from the code. >>> >> >> OK, what are the similarities? >> >> >>> The most confusing part is the ExecServer. If someone can give some >>> details for what is used, it would be great. >>> >> >> First, I would ask you to use one of the IntelliJ or Astah tools to >> generate class diagrams for all aspects of the OODT projects which include >> XMLRPC functionality. This way the structure and communication is explicit. >> Once you've done this, please reply to this thread and we can forward the >> conversation. >> >> >>> And one more question related to it "can't find anywhere is the OODT >>> code that the callLocalServerManager method be called". >>> >>> >>> Neither can I right now. For the time being please progress with the >> class diagrams as described above. I will keep searching for this and we >> can touch base here once we've located it. >> Thanks >> Lewis >> >> > > -- *Lewis*
