I have a WSDL that worked fine with 2.0.7. I upgraded to cxf 2.1.3-SNAPSHOT
(so I could upgrade to Servicemix 3.3-SNAPSHOT) and I was still able to
generate my classes from my WSDL with it, but, I get an error at runtime
when I try to send a request from my client. The relevant part of the stack
element is referring to an undefined wsdl:message element." Sorry for
> the trouble.
>
> Glen
>
>
> 2008-06-21 Ryan Moquin wrote:
> > Definitely. It sounded to me like a more general error that could be
> made
> > more specific. I'll file a bug for it for you
on: Header message not defined in service
> > >> model.
>
>
>
> 2008-06-19 Daniel Kulp wrote:
> > On Jun 19, 2008, at 10:59 AM, Ryan Moquin wrote:
> >
> > > Never mind.. I figured out the problem finally. If you have a
> > > soap:header
> > >
m.. 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 servic
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 messa
