First and foremost, check that the run time wsdl generated by the service matches the service you used to create that service.
It's highly likely that you'll find it has "different" namespaces, for the types particularly. It's very common that the schema section uses an xml namespace derived from the java package name, rather than the xmlns defined in the source wsdl. This is a "misconfiguration" But what is the "right" config? Well, that's a different matter.... ;) I'd offer you our configs, but we're still fighting issues like this intermittently, and have no good example of something that always works. Cheers, Karl P > -----Original Message----- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Chris Mathrusse > Sent: Tuesday, February 06, 2007 11:17 PM > To: [email protected] > Subject: [xfire-user] Inbound parameter contains no data > > I generated my classes from a known good WSDL. (Both client > and server) The service is defined and appears to be > functional when the server is started. I can send data into > the server via the Eclipse Web Services Explorer. Here the > inbound parameters are populated with the data that I entered > via the Web Services Explorer. > > When I attempt to send data into the service via the Client > that was generated, my parameter is not null but it contains > nulls for all of the fields defined within it. I've made no > modifications to the generated code. Everything appears to be > correct and my client does establish a connection to the > server. It simply appears to have lost the data contained > within the passed in object. > > Any suggestions would be greatly appreciated... > Thanks for the help.... > > > --------------------------------------------------------------------- > To unsubscribe from this list please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
