ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominic Pöllath <d.poell...@adito.de>
Subject Re: problems with external definition
Date Tue, 01 Jan 2013 09:31:44 GMT
Hi tammo!

thank you for your good answer. it's an understandable reason, to not 
support the remote references.
wish you a happy new year. :)


best regards
dominic



-----Ursprüngliche Nachricht----- 
From: Tammo van Lessen
Sent: Monday, December 31, 2012 7:30 PM
To: user
Subject: Re: problems with external definition

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 <d.poellath@adito.de>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 

Mime
View raw message