Arun Gupta wrote:
>
> Somehow the wsdlModel in the created Dispatch is null and the change
> made in [1] is causing WS-Addressing not to be enabled, even though all
> the features are set correctly on the client side. That's why no
> WS-Addressing headers are generated.
>
> I've added a test in our workspace (wsa.fromwsdl.custom.testCustomFault)
> for this condition. I'll continue digging for more information and keep
> you updated.
>
Is the test passing or failing?
> Can you please file an issue on Issue Tracker though ?
>
Done.
Thanks,
--Ryan