gnodet wrote: > > Please raise a JIRA for that. > If you have a working test case, could you please attach it ? > ... and any fix you may have, of course ;) > > On 10/10/06, Fabrice Dewasmes <[EMAIL PROTECTED]> wrote: >> >> to give some more informations. Problem is coming from WSDLReader with >> this >> error : >> >> 14:01:27,344 WARN [EndpointRegistry] Error retrieving interfaces from >> service description: WSDLException (at /definitions/import): >> faultCode=OTHER_ERROR: Unable to resolve imported document at >> 'porttypedef.wsdl'.: This file was not found: >> file:/R:/java/tools/jboss/4_0_3-eici/bin/porttypedef.wsdl >> >> Fabrice >> >> >> >> Fabrice Dewasmes wrote: >> > >> > Hi, >> > >> > When you try to deploy a http provider endpoint, the target WSDL is >> > parsed. If the targetNamespace of the targeted service is different >> from >> > the endpoint namespace, the targeted wsdl is imported and operations >> are >> > replicated to build the endpoint internal WSDL. >> > >> > But when a consumer proxies this provider, it parses the internal WSDL >> but >> > fails to find the imported WSDL. I think this is a bug. >> > >> > Oh I forgot to mention that I'm using the servicemix-web packaging. >> > >> > Fabrice >> > >> >> -- >> View this message in context: >> http://www.nabble.com/http-endpoint-wsdl-generation-bug---tf2410853.html#a6734918 >> Sent from the ServiceMix - User mailing list archive at Nabble.com. >> >> > > > -- > Cheers, > Guillaume Nodet > > -- View this message in context: http://www.nabble.com/http-endpoint-wsdl-generation-bug---tf2410853.html#a6755768 Sent from the ServiceMix - User mailing list archive at Nabble.com.
