Never mind.. I figured out the problem finally. If you have a soap:header element referring to a message that doesn't exist, you apparently get this message... which is so hard to find due to the message, but due to the fact that I haven't found any tools that will catch this problem.. I just happened to figure out the problem by trial and error....
On Thu, Jun 19, 2008 at 12:32 AM, Ryan Moquin <[EMAIL PROTECTED]> wrote: > Hello, > > I'm upgrading to a new version of servicemix and therefore upgrading to use > CXF 2.0.7 since that's what servicemix was tested with. For some reason > though, I'm getting the follow message during my build when CXF attempts to > process one of my WSDLs: > > java.lang.RuntimeException: Header message not defined in service model. > > Can someone tell me what that means specifically? I didn't get this error > in 2.0.1. Also, if I look at another WSDL I have that uses headers, I > don't see any difference, yet that one processed correctly through 2.0.7. > I'm hoping someone can get me on the correct track to resolve this problem. > > Thanks!! >
