In general, if a full mvn based test case is attached to the JIRA, it’s much more likely to be fixed. Spending a lot of time trying to reproduce a problem isn’t something many of use are willing to do.
We have tests in the test suite that shows SwA working and the JAX-WS tck’s that various vendors that use CXF run also test SwA. Thus, it’s definitely working for various known cases. Without a full test case, I’d have no idea where to even start looking on how to reproduce it. Dan > On Nov 23, 2016, at 7:27 AM, Sergey Beryozkin <[email protected]> wrote: > > Hi Diego > > While it is probably fair to say a JAX-WS with SWA is not the most widely > feature these days, the real reason no immediate fix is coming is that we do > not have that many resources. > CXF users often help with their own patches. Please consider providing a > fix... > > Sergey > On 22/11/16 08:30, Diego Pietralunga wrote: >> Hello. >> >> Any chance someone addresses CXF-7131 on Jira? >> https://issues.apache.org/jira/browse/CXF-7131 >> >> At least to determine if it IS a CXF framework problem or not. >> >> We have to make decisions on adoption in a company project. >> I really would like to pick up Apache CXF but (unless it's a kind of >> configuration issue of mine..) >> in our scenario it's more troblesome than not and... to be honest, one of >> the things >> that could drive adoption is responsiveness of the community but... neither >> a previous mail >> of mine to the users list nor the Jira issue has been addressed... >> Is it a niche scenario? >> JAX-WS is no more so "hot" these days (and it's not taken care that much) ? >> >> Cheers. >> >> Diego >> >
