Any chance you could strip the wsdl down a bit and create a small test case (no business logic and such)? I'd love to try and see what is going on here.
Dan On Wed January 27 2010 10:06:46 am [email protected] wrote: > yes, it is with JAXB. > > > the annotations of the bean : > > @XmlAccessorType(XmlAccessType.FIELD) > @XmlType(name = "CheckCriteriaAddressViewForCheckAddressRequest", propOrder > = { > "maxWishedResults", > "checkType", > "formattedPostalAddressView", > "returnGeographicCoordinates", > "typography", > "maxStreetNameList", > "maxCityNameList", > "localReturnCedex", > "localWildCardUse", > "localReturnLocalityGeocoordinate", > "localReturnDemographicData", > "localSpecialAddress", > "localReturnRivoli", > "localInteractive", > "localListResolve", > "localListDuplicatedStreet" > }) > > > > For the message : > @XmlAccessorType(XmlAccessType.FIELD) > @XmlType(name = "CheckAddressMessage", propOrder = { > "postalAddress", > "checkCriteriaAddress" > }) > public class CheckAddressMessage { > > @XmlElement(name = "PostalAddress", required = true) > protected PostalAddressViewForCheckAddressRequest postalAddress; > /** > * > */ > protected CheckCriteriaAddressViewForCheckAddressRequest > checkCriteriaAddress = new > CheckCriteriaAddressViewForCheckAddressRequest(); ... > > > And the interface of the service: > > public java.util.List<types.PostalAddressViewForCheckAddressResponse> > checkAddress( > @WebParam(name = "PostalAddress", targetNamespace = "") > types.PostalAddressViewForCheckAddressRequest postalAddress, > @WebParam(name = "CheckCriteriaAddress", targetNamespace = "") > types.CheckCriteriaAddressViewForCheckAddressRequest > checkCriteriaAddress > throws .... ; > } > > > > Maybe it's because in the message the annotation of the element which have > the problem (ie : checkCriteriaAddress ) is missing ? > (all the code is generated by cxf wsdl2java) > > > > > > > 2010/1/27 Daniel Kulp <[email protected]> > > > On Tue January 26 2010 5:49:56 am [email protected] wrote: > > > Hi again, > > > > > > the problem was that the object not mapped started with a uppercase > > > when request generated by SOAPUI (not working) > > > and a lower case when I use java to call the service. > > > > > > Yet the name of the element starts by an uppercase in the wsdl, so I > > > > don't > > > > > know why it's matching with a lowercase, and not with a uppercase. > > > > > > Did someone had this kind of problem? > > > > I've definitely never seen this before. Not good. Is this with JAXB? > > What > > do the annotations look like in the JAXB bean and on the method? > > > > Very strange. > > > > Dan > > > > > 2010/1/26 <[email protected]> > > > > > > > I just tried to call the service via java, and it's working. > > > > > > > > Some ideas why it's not working using a soap client ? > > > > > > > > 2010/1/26 <[email protected]> > > > > > > > > Hi everybody, > > > > > > > >> I'm trying to call a web service using SOAPUI, and I've a problem > > > >> with one of the two complex elements I'm sending to the server. > > > >> The server catch the request, and create the type of the first > > > >> element in java, and set it with the good values, but it does not do > > > >> it for > > > > the > > > > > >> second element. > > > >> No problem seems to occurs, and I've do the same operations to > > > >> create this new web service as I've do with others. > > > >> > > > >> Did anyone had met this problem, like the conversion xml >> java > > > >> looks like not working ? > > > >> What can I do to find a way to fix that ? > > > >> > > > >> thx > > > >> > > > >> Pierre > > > > -- > > Daniel Kulp > > [email protected] > > http://www.dankulp.com/blog > -- Daniel Kulp [email protected] http://www.dankulp.com/blog
