ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Ousov <aou...@gmail.com>
Subject Re: calling BPEL from another BPEL
Date Mon, 01 Dec 2008 10:02:24 GMT
Hello Alex.
>> 2. Strange bug. Both caller and calling processes seems to share cached
>> data, especially this concerns xslt stylesheets. So if caller and calling
>> processes both have xslt stylesheet with *the same name*, doing
>> bpws:doXsltTransofrm from both processes with xslt url relative to process
>> (just file name) can take wrong stylesheet (in fact stylesheet of last
>> deployed process). It took a lot of time to track this down.
> This is unrelated to process-to-process communication but is nonetheless a
> bug.   I thought we had an outstanding  Jira issue about it (it was reported
> before on the mailing list) but I couldn't find it so I created a new one:
> https://issues.apache.org/jira/browse/ODE-439
You were right, there is nothing about interprocess communication. I 
attached simple test processes to bug report in case you need it.
> 3. Cached wsdls are also take place. So if caller and calling processes both
>> use same but little modified wsdl (in my case fault names were different)
>> BPEL process cannot find fault by name, because wrong wsdl were cached and
>> used.
> Again, probably unrelated to process-to-process communication and more about
> the isolation between deployment packages.   I'm not aware of any bug in
> this area (WSDL caching or sharing) so if you have a reproducible test case,
> it would make it easier for us to track down and fix.
It is still complicated and not unclear to me, what is happening. If 
I'll have clear test case, I'll write it down here.
> alex

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message