Hi, I'm using xFire 1.2.6 to create a WebService from an interface (and class). The WebService is working correctly when I deploy my application on a jBoss machine.
The problem is when trying to deploy the same WebService on a WebSphere 7 machine. It looks like the auto generated WSDL file (Which was generated correctly on jBoss) is wrong. In particular, I think xFire does not take the correct class when generating the WSDL, when running on WebSphere. I have a class named "Component" with 3 members, however, in my WSDL I get the "Component" type, with a wrong list of members, as if it found a different class and used it instead of my class. I have tried using the full qualified name of my class, but it didn't work. Any ideas? Did you ever see this behaviur on WebSphere server? Thanks Guy Hudara -- View this message in context: http://www.nabble.com/xFire-Does-not-find-the-correct-class-when-generating-the-WSDL.-tp23197442p23197442.html Sent from the XFire - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
