ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Boisvert <boisv...@intalio.com>
Subject Re: How to modularize a large BPEL process definition?
Date Thu, 13 Aug 2009 14:55:51 GMT
The natural (but somewhat painful) way would be to create sub-processes for
each of these parts and invoke them from the main process.   If there's a
strong pattern between all of them, you could use templating techniques
(e.g. Velocity) to keep your BPELs DRY (don't repeat yourself) and avoid


On Thu, Aug 13, 2009 at 3:51 PM, kodeninja <koffee.2.kode@gmail.com> wrote:

> Howdy,
> I have a pretty large BPEL file (> 12000 LoC) that's become quite unwieldy
> now. Opening it up in the NetBeans/Eclipse BPEL editor itself is a pain and
> maintaining it is really difficult. What are the best practices to
> modularize a large BPEL file?
> Part of the reason it's so large is because I have a retry logic
> implemented
> on all the "invoke"s that happen within the BPEL. This code is pretty much
> the same for all the invoke calls and has led to a lot of duplication. Is
> there a way I can, say, create a reusable function which can be used in the
> invoke calls rather pasting the same retry logic again and again? Or maybe
> a
> way to break down the main BPEL into smaller BPEL processes that can be
> invoked from the main BPEL?
> Basically, I'm looking for ways to manage this complex BPEL process. Any
> suggestions/comments?
> Thanks,
> -Kodeninja
> --
> View this message in context:
> http://www.nabble.com/How-to-modularize-a-large-BPEL-process-definition--tp24954577p24954577.html
> Sent from the Apache Ode User mailing list archive at Nabble.com.

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