issing MessageID, I believe you're correct in that this
is probably another issue, especially in the case where addressing is
optional but some properties must be present with other properties in cases
where they are sent. I didn't have a chance to look into this at all as I
was only conc
Logged an issue in Jira with potential patch. See
https://issues.apache.org/jira/browse/CXF-2629
Rebecca
dkulp wrote:
>
> On Fri December 4 2009 11:15:27 am rduhard wrote:
>> I think that the following line of code might be the culprit:(via the
>> MAPAggr
tMaps =
> ContextUtils.retrieveMAPs(message, false, true);
> AddressingProperties inMAPs =
> ContextUtils.retrieveMAPs(message, false, false);
> if (outMaps != null && outMaps.getFrom() == null && inMaps !=
> null) {
&
equest. Let me know if this change
> would address your interop requirement.
>
> Cheers,
> Eoghan
>
> 2010/1/6 Craig Tataryn
>
>> Was wondering if anyone knew the answer to this? We need this for
>> interoperability testing with our vendor.
>>
>> Craig.
Is there a way to have CXF generate the MAP on the outgoing
response message? It seems to only generate To, Action, MessageID and
RelatesTo elements. The client requires the the From element also be
populated, but I haven't been able to find a way to have it included.
element is NOT anonymous
d. Please log a bug and attach
> a
> small test case if you can. (like modify the hello world or something)
>
> Actually, you kind of have two bugs. The "required" bug and the
> messageID/ReplyTo thing.
>
> BTW: What version of CXF?
>
> Dan
>
Is it possible to have CXF reject messages with a Fault automatically for
endpoints that require Addressing where the request is either missing them
altogether or missing certain required fields (i.e. missing messageID when
ReplyTo is present)?
Currently if a client sends a request without MAPs i
wn.Thus, we grab the
>> SOAPAction. However, we should be resetting the SOAPAction to the
>> Action.
>> (although, if you are using SOAP 1.1, I would probably argue that your
>> wsdl is then "not correct" and the SOAPAction and Action should be set
>&g
ting the SOAPAction to the Action. (although,
> if
> you are using SOAP 1.1, I would probably argue that your wsdl is then "not
> correct" and the SOAPAction and Action should be set to the same)
>
>
> Dan
>
>
>
>>
>> Thanks,
>>
>>
I'm currently implementing WS-Addressing in my web service and am a little
confused about the way CXF is populating the wsa:Action property on the
response message. Our WSDL (provided, not created) defines an input and
output message like this with corresponding wsaw:Action attributes defined:
10 matches
Mail list logo
