Ok I'll try to whip up a test case and get it posted asap. I'm using the latest release 2.2.5 of CXF.
Thanks! dkulp wrote: > > > This SOUND like a bug. If wsdl:required="true" is there, according to > spec, > that implies that the addressing is required. 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 > > > On Thu December 17 2009 8:06:34 pm rduhard wrote: >> 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 it ignores that fact >> and >> processes as normal (all i get are warnings in my console) or if there >> are >> missing elements (i.e. messageID), it eventually faults out on a null >> pointer exception when anything tries to process these non-existent >> addressing properties.. it seems like CXF should recognize before then >> that >> certain properties (or all) are missing and fault out before continuing. >> >> I have the following defined in my WSDL:binding >> <wsaw:UsingAddressing wsdl:required="true" /> >> >> and also have the following within my spring endpoint configuration: >> <jaxws:features> >> <wsa:addressing/> >> </jaxws:features> >> >> Is there a way to do this in CXF and I'm maybe missing something or is >> this >> the expected behaviour? >> >> Thanks, >> Rebecca >> > > -- > Daniel Kulp > [email protected] > http://www.dankulp.com/blog > > -- View this message in context: http://old.nabble.com/CXF-return-fault-when-WS-Addressing-MAPs-are-not-present--tp26837662p26876361.html Sent from the cxf-user mailing list archive at Nabble.com.
