Hi Dominic, since BPEL process instances may be long-running, we decided to not support remote references to WSDLs, since raises a bunch of questions: When would the remote WSDL be loaded, what would happen if the WSDL changed meanwhile, etc. Thus, the process author needs to get the definition and "package" it along with the process and deployment descriptor. If the WSDL changes, a new version of the process can be deployed and the process versioning mechanism of ODE kicks in to route the messages to the correct version.
tl;dr: yes, this is intentional ;) HTH, Tammo On Mon, Dec 31, 2012 at 6:29 PM, Dominic Pöllath <[email protected]>wrote: > hi! > > i got a strange problem, while implementing the IL. while triing to > receive the Definition Object with > ProcessConf.getDefinitionForService(QName pServiceName) > > i’ll get null, because the wsdl file is an external file (http:// ...), > but i was asking myself, why this is happening. > the wsdl definition obj. could be easily provided by the WSDLReaderImpl > from the woden project (also in the bpel api, afaik) > but at the point of implementing the IL it’s a complicated task. > > do i missing something here? is there a default rout for external wsdl > sources? or do i have to get the definition by self? > > > best regards, > dominic -- Tammo van Lessen - http://www.taval.de
