DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15284>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15284 Proposed modification to OperationDesc Summary: Proposed modification to OperationDesc Product: Axis Version: 1.0 Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Basic Architecture AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I'm working on an project where we want to expose our generic business logic classes as webservices. However, each of the methods in these classes expect the first parameter to be a server side (application context) object that should not be supplied by the client. A servlet filter creates the appContext object and makes it available for the server side classes to use (including our custom Axis Provider). In our custom Axis provider, we are overriding the invokeMethod(..) method to inject the appContext object into the argument array before invoking the method. That seems to work ok. However, the generated WSDL still has the offending (supplied on the server side) parameter in it which we don't want the client applications to have to worry about. Our initial thoughts on how to get rid of the parameter from the WSDL is to override the initServiceDesc(..) method in our custom Provider and remove the offending ParameterDesc from the OperationDesc object. Unfortunately, there doesn't seem to be any method available to remove a parameter from an OperationDesc. What we really want to do is to supply our own list of ParameterDesc objects (with the offending one removed). There was a partially implemented setParameters(..) call already in the OperationDesc class. To make our solution work, we fixed/completed the implementation of the setParameters(..) method and made it public. We are now able to remove the parameter from the WSDL (by overriding initServiceDesc(..) in our provider) and it seems to work. If there are no objections, I'd like to have someone add this patch to the main source tree. Below is the source for the method we had to modify. ----------------------- In OperationDesc.java: ----------------------- /** * Set the parameters wholesale. * * @param newParameters an ArrayList of ParameterDescs */ public void setParameters(ArrayList newParameters) { parameters = new ArrayList(); //Keep numInParams correct. numInParams = 0; for( java.util.ListIterator li= newParameters.listIterator(); li.hasNext(); ){ addParameter((ParameterDesc) li.next()); } }
