This is just a configuration problem. The servicemix-http BC will generate a wsdl based on the wsdl from the target endpoint if available. This means: * the target endpoint must have a wsdl description * the target endpoint must be activated before the http BC endpoint.
On 4/18/07, ib22841 <[EMAIL PROTECTED]> wrote:
What kind of problem is it? Is it a natural limitation of JBI spec? Hard to believe. It might be a limitation of jbi implementation of servicemix/fuse. In this case it should be filed as bug/enhancement. Does anybody know more about that? Regards, Ilja gnodet wrote: > > >> 3. I've built my message definitions as complex types completely in XSD >> then >> expose them into WSDL using xsd:include. But I'm having problems with >> the >> HTTP consumer endpoint loading them on deployment. In fuse (1.2.2), it >> can't find them on the classpath. Also, in the Web Services explorer, >> it's >> getting errors trying to load in the included XSDs, but I'm more >> concerned >> about the former issue. > > Importing xsds / wsdls may lead to problems, as one limitation of jbi, is > that > endpoint description must be standalone (no imports at all), which is > actually > not always possible. > > -- > Cheers, > Guillaume Nodet > ------------------------ > Architect, LogicBlaze (http://www.logicblaze.com/) > Blog: http://gnodet.blogspot.com/ > > -- View this message in context: http://www.nabble.com/A-few-questions-about-SEs-and-WSDL-tf3053641s12049.html#a10055985 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet ------------------------ Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
