JADE Environment Development Ideas

When a third party Web Service WSDL is imported into JADE to create a JadeWebServiceConsumer class, there are also proxy classes generated to be used as input and output parameters to the generated webService methods. These generated classes are transient only, and changes to them cannot be made as they would be lost if the WSDL is re-imported. If an imported WSDL has complexType input parameters, then the "structure" of transient objects that a consumer JADE developer needs to create to enable the webService method to be called might be significant, including collections of sub-objects from the parent parameter instance. The issue for the developer is that they need to keep track of all these created objects to ensure they are deleted after the webService call, to ensure that the transient objects are not leaked. It would be great if the generated classes also had a delete method generated that deleted any singleton "sub-objects" and purged any collections of sub-objects that are part of the input parameter.
Note that the objects created as part of a response to the webService are all managed by the JadeWebServiceConsumer, and deleted via a reset or the deletion of the consumer instance, but there is no easy way to manage this for input parameters, except by using a destructor.