http://technology.amis.nl/2007/06/04/serve-up-your-bpel-processes-as-templates/?utm_source=rss&utm_medium=rss&utm_campaign=serve-up-your-bpel-processes-as-templates Fri, 12 Apr 2013 10:04:09 +0000 hourly 1 http://wordpress.org/?v=3.5.1 http://technology.amis.nl/2007/06/04/serve-up-your-bpel-processes-as-templates/#comment-4613 Sjoerd Michels Thu, 07 Jun 2007 08:08:04 +0000 http://technology.amis.nl/blog/?p=1812#comment-4613 As Marc rightfully points out, BPEL templating (in release 10.1.3.1) has its limitations. We find it useful for communicating and demonstrating particular concepts in bits and pieces of BPEL code. Typically, the template uses BPEL Empty constructs stating something like yourPartnerLinkCallGoesHere. Be carefull when creating large templates: when you find yourself reusing large BPEL processes your process decomposition may be in need of revision.

]]> http://technology.amis.nl/2007/06/04/serve-up-your-bpel-processes-as-templates/#comment-4612 Marc de Brouwer Mon, 04 Jun 2007 12:18:55 +0000 http://technology.amis.nl/blog/?p=1812#comment-4612 You have to be careful with this feature, though.
It will not rename namespaces in all files that are included in the template.
Notably, it does not replace namespaces in wsdl and xsd files.
This can lead to frustrating conflicts when you edit those xsd and/or wsdl files so they have conflicting definitions in the same namespace.

]]>