On 1/22/06, Aaron Evans <[EMAIL PROTECTED]
> wrote:
Ajith Ranabahu <ajith.ranabahu <at> gmail.com> writes:
>
>
> Hi Aaron,
> This is a bug in the newly introduced options class. We actually found
> the problem few days back and fixed it in the latest codebase.
> The problem is that the stub wise options object (you'll see this when
> you open the generated stub code) attaches itself to the operation
> clients options object once a method has been called!
> Here is the fix if you have the .94 code. (Unfortunatley I can't think
> of a workaround that does not include manipulating code :()
>
> Open the org.apache.axis2.client.Options class in the core module.
> at line 223 change the soapAction = parent.getSOAPAction();
> to return parent.getSOAPAction();
> Now that method should look like this
> public String getSoapAction() {
> if (soapAction == null && parent != null) {
> return parent.getSoapAction();
> }
> return (soapAction != null) ? soapAction : "";
> }
> Other getter methods also need to be modified in this way but essentially this
is the method that would make the difference.
> Ajith
>
Thanks, I will do the above patch in my environment. One question though, you
say that "other getter methods also need to be modified in this way". Is this
restricted to the axis core source or do I also need to patch my generated stub
at all?
aaron
--
Ajith Ranabahu
