Please Publish Announced Workaround to Bpel Deployment Nightmare

Question

Oracle's own Product Director and Senior Product Manager describe the horror in their document published on Oracle's own site Kevin Clugage and Robin Zimmermann.
http://www.oracle.com/technology/products/ias/bpel/pdf/bpel-admin-webinar.pdf
They put my feelings best where they show a photo of a guy trying to pull his hair out on the one of the "Deployment Challenge" slides.
I do not know why Oracle has chosen to break three very fundamental rules most anyone has ever had to work with:
1. Never put machine or deployment specific code in a source file
2. Never tell a user NOT to modify a file and then tell him to modify that same file if he wants to deploy.
3. Never publish a known horror, announce that there is a workaround, and not publish the workaround in great detail.
It is even more confusing why there isn't a huge outcry from customers. The only conclusion I can come to is there aren't enough customers to even care, I just don't know. Either way, I need guidance, as
They cite in this document the standard deployment situation for ANYTHING built in any normal situation. It is always expected to be built and deployed on at least these machines
* developerOne's machine
* developerTwo's machine
* developerThree's machine
* test server
* QA server
* production server
What I need is for Kevin Clugage and Robin Zimmermann to produce documentation for the workaround they published in the above document, and especially how to do it in a way that respects the instructions found in my wizard built files. (" DONOT EDIT THIS JDEV GENERATED FILE") I don't want to fix one problem and create another.
It would embarrass Oracle and my employer both if it were documented how much time we have wasted attempting to address this ridiculously simple issue over the past several months. Some reasonable urgency would be in order.

Answer 1

I have used this document to deploy my BPEL processes, and I didn't have to edit the build.xml.
For every BPEL process that calls a partner link I create a pre-build.xml and a post-build.xml. These scripts are called by default. You will also need to have a properties file for every environment you want to deploy to.
Here is an example of these files, please note these are specific to my environment by you will hopefully get an idea on how to achieve this.
pre-build.xml
<?xml version="1.0"?>
<project name="bpel.pre-build" default="pre-build" basedir="./bpel">
<property name="explicitErrorHandlerDeploy" value="http://${http.hostname}:{http.port}/orabpel/default/explicitErrorHandler/1.0/explicitErrorHandler?wsdl"/>
<property name="ConvertVariablesDeploy" value="http://${http.hostname}:{http.port}/orabpel/default/ConvertVariables/ConvertVariables?wsdl"/>
<property name="GetProfilesDeploy" value="http://${http.hostname}:{http.port}/orabpel/default/GetProfiles/1.0/GetProfiles?wsdl"/>
<target name="pre-build">
<bpelc input="${basedir}/bpel.xml" rev="${rev}" deploy="default" force="true">
<customize>
<partnerLinkBinding name="explicitErrorHandler">
<property name="wsdlLocation">${explicitErrorHandlerDeploy}</property>
</partnerLinkBinding>
<partnerLinkBinding name="ConvertVariables">
<property name="wsdlLocation">${ConvertVariablesDeploy}</property>
</partnerLinkBinding>
<partnerLinkBinding name="GetProfiles">
<property name="wsdlLocation">${GetProfilesDeploy}</property>
</partnerLinkBinding>
</customize>
</bpelc>
<copy file="bpel.xml" tofile="bpel_orig.xml" overwrite="true"/>
<copy file="_bpel.xml" tofile="bpel.xml" overwrite="true"/>
</target>
</project>
post-build.xml
<?xml version="1.0"?>
<project name="bpel.post-build" default="post-build" basedir="./bpel">
<target name="post-build">
<echo>
| Copying bpel_orig.xml to bpel.xml
</echo>
<copy file="bpel_orig.xml" tofile="bpel.xml" overwrite="true"/>
</target>
</project>
properties file
domain = default
rev = 1.0
admin.user = oc4jadmin
admin.password = password
http.hostname = server.domain
http.port = 7777
opmn.requestport = 6003
oc4jinstancename = oc4j_soa
Really the onlt thing that will change between BPEL processes is the pre-build.xml script, and this will be dependent on what partnerlink you are calling.
Please remember when deploying you need to right-click the build.xml file and choose Run Ant. Before you press OK choose the properties file you want to use dependent on the environment you are deploying to. You do this by selecting the properties tab in the Run Ant (Bottom Box).
Cheers
James