On Tue April 14 2009 6:14:29 am Gabo Manuel wrote: > Hi Dan, > > Any update on this issue? I mean, if there is a work around (use Aegis > data binding perhaps?)?
Just logged a JIRA: https://issues.apache.org/jira/browse/CXF-2172 The workaround would be to pull the XmlRootElement annotation off the object if that is at all possible. That said, I'm testing a fix now. Hopefully tomorrows snapshots would have it fixed. Dan > > Thanks in advance. > > Gabo > > P.S. Did you receive the attachment in my previous reply? > > Daniel Kulp wrote: > > On Tue March 31 2009 12:04:05 am Gabo Manuel wrote: > >> Hi Dan, > >> > >> I saw your latest comments re the jira. Would that mean that CXF has a > >> problem generating the WSDL properly? Or is there an annotation I should > >> fix? > > > > Ah. Didn't realize this was a "java first" thing producing that wsdl. > > The JIRA item just really mentioned running wsdl2java on the wsdl. > > > > In anycase, it MAY be an issue with the annotations, but I'm not really > > sure what it would be. I thought it would be a missing > > @XmlType(name="MyObject") annotation on the MyObject thing causing no > > "type" to be generated, but the wsdl was generated with the element and > > complex split so that doesn't appear to be it. > > > > Hmmm.... Any chance of getting the code that caused that wsdl? At > > least the SEI interface and the objects? > > > > Dan > > > >> Gabo > >> > >> Daniel Kulp (JIRA) wrote: > >>> [ > >>> https://issues.apache.org/jira/browse/CXF-2136?page=com.atlassian.jira. > >>>pl > >>> ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693904#a > >>>cti on_12693904 ] > >>> > >>> Daniel Kulp commented on CXF-2136: > >>> ---------------------------------- > >>> > >>> > >>> Actually, this is not a valid wsdl according to WSI-BP rules. For > >>> RPC/Lit, the parts in the message MUST be defined as a type, not an > >>> element. A couple of the operations above are using <wsdl:part > >>> element="tns:MyObject" name="myObject"> for input parts, and that's > >>> not valid for RPC/Lit. > >>> > >>> The error message could be improved and I'll work on that a bit, but > >>> this issue is invalid. > >> > >> Daniel Kulp wrote: > >>> Hmmm... in RPC/Lit, those checks shouldn't be applying. The zip got > >>> stripped off by Apache's mailer. Could you file a JIRA and attach? > >>> > >>> Thanks! > >>> Dan > >>> > >>> On Wed March 25 2009 5:55:20 am Gabo Manuel wrote: > >>>> Hi All, > >>>> > >>>> I have a service deployed using CXF and was planning to test it using > >>>> a CXF client as well. Attached is a zip file containing the service > >>>> and the wsdl generated. > >>>> > >>>> However, when I issue the following: > >>>> > >>>> D:\java\cxf\apache-cxf-2.2\bin>wsdl2java -ant -client > >>>> -autoNameResolution -exsh true -d ClientDir MyObjects.wsdl > >>>> > >>>> WSDLToJava Error: Non unique body parts! In a port, operations must > >>>> have unique operation signaure on the wire for successful dispatch. In > >>>> port {http://domain.some/}MyObjectServicePort, Operations > >>>> "{http://domain.some/}insertMyObject"; and > >>>> "{http://domain.some/}updateMyObject"; have the same request body block > >>>> {http://domain.some/}MyObject > >>>> > >>>> I could be missing something basic, maybe some option in wsdl2java or > >>>> something. It's a bit odd that the wsdl that was created by CXF cannot > >>>> be translated by its own wsdl2java. :D > >>>> > >>>> Thanks in advance. > >>>> > >>>> Gabo > > > > ------------------------------------------------------------------------ > > > > > > No virus found in this incoming message. > > Checked by AVG - www.avg.com > > Version: 8.0.238 / Virus Database: 270.11.33/2031 - Release Date: > > 03/30/09 17:56:00 -- Daniel Kulp dk...@apache.org http://www.dankulp.com/blog
