Hi All,
     Does anyone has any thoughts why it was initially decided to have
the kind of packaging we have in the WSDL tool as of now?
     I had a look into the Axis java tool and the folder structure is
quite simple. In C++ wsdl tool we have the cpp folder which implies RPC
and literal folder that implies document literal. 

     Also, we do not have any document (at least comments) on how
org/apache/axis/wsdl/wsdl2ws/cpp/ClientStubWriter.java differs from
org/apache/axis/wsdl/wsdl2ws/cpp/literal/ClientStubWriter.java. Could
anyone please tell me how they differ please? As far as I can see,
org/apache/axis/wsdl/wsdl2ws/cpp/literal/ClientStubWriter.java derectly
inherits org/apache/axis/wsdl/wsdl2ws/cpp/ClientStubWriter.java and
despite that the derived class implement so many methods in base class
as is (resulted from copying code most probably) despite the fact that
the methods are already inherited.
  
    If I am to fix these and remove duplication, I would have only the
org/apache/axis/wsdl/wsdl2ws/cpp and would drop literal package. I would
have one generic base class
org/apache/axis/wsdl/wsdl2ws/cpp/ClientStubWriter.java and have RPC and
Doc lit styles inherit from this. I would do the same for other classes
as well. I am not sure how keen the community would be to have this kind
of a refactoring on the tool. Basically as a developer I am wasting so
much time, dplicating some of the changes from RPC to Doclit at times as
well as spend lot of time understanding the differences in classes in
org/apache/axis/wsdl/wsdl2ws/cpp and
org/apache/axis/wsdl/wsdl2ws/cpp/literal

Thanks,
Samisa...

Reply via email to