Thanks, Aki. What I'm going to do is something from scratch to replicate this issue, and sent it out to you.
In the meanwhile, I've manually updated some of the generated code by wsimport and it is working fine. On Tue, May 6, 2014 at 5:27 AM, Aki Yoshida <[email protected]> wrote: > you should be getting the correct request messages using the generated > code. > if this is not the case, we have to take a look. > > maybe you can remove irrelevant parts and rename urls/names to obscure > the sensitive part of your wsdl so that we can look at it. > > regards, aki > > 2014-05-02 23:22 GMT+02:00 Ubaldo Villaseca <[email protected]>: > > First of all, apologize not to provide sample source code. Working in a > > project with some sensitivity about Internet DLs and groups. > > > > Question. Did you ever get a wrong SOAP XML request even if it was > > automatically generated? > > > > I'm having that problem. SOAPUI manages to work just fine, but wsimport > or > > wsdl2java don't. > > > > 2nd question, to fix that, I'm manually updating the generated class > > ObjectFactory, where the _*_QNAME are defined, and changing the namespace > > and/or name to what is expected. Is this safe or I'm just giving pain > > killers to the patience rather than healing it? > > > > Working with CXF 2.7.11, JAX-WS 2.2, Java 7. > > > > Thank you! >
