Arun Gupta wrote:
> Further update ...
>
> If I create Dispatch with WSDL, then wsdlModel is not null and all
> WS-Addressing headers are populated correctly. Here is the code that
> worked for me:
>
> -- cut here --
> -- cut here --
>
> Now wsdlModel is required for WS-Addressing to work. Do you have access
> to the endpoint WSDL where the fault is dispatched to ? If yes, then try
> creating the service this way and it should work. If not, then your
> question gets morphed into:
>
When you say "Now wsdlModel is required for WS-Addressing to work", do you
mean that is the correct behavior or the current behavior?
I'm not sure what the wsdl is needed for. In WS-TX, we have wsdl files
for ws-at and ws-coor, but there are no faults specified and all required
operations are one-way. Furthermore, there is no dynamic retrieval of
the wsdl files at runtime in WS-TX.
> How to create a Dispatch (w/o WSDL) such that WSDL model is correctly
> populated ?
>
...and is there an answer? ;8-)
--Ryan