ADF Binding Service Names Must Be Unique Across All Deployed SOA Composite Applications

All ADF bindings must have a unique service name across all deployed SOA composite applications.

For example, assume you perform the following steps:

Build and successfully deploy a SOA composite application that includes multiple composites to the SOA server.
Change one of the composites in the SOA composite application by adding new components and an outbound external reference.
Compile and successfully build the updated SOA composite application as revision 2.0.

Deploy the updated SOA composite application to the same partition or a different partition.

You can receive the following error:

<Oct 7, 2013 11:52:01 AM EDT> <Error> <ServletContext-/soa-infra>
<BEA-000000> <Error during deployment
oracle.fabric.common.FabricException: Deployment Failed: The serviceName
attribute "OrderProcessorService" has already been used.   ServiceName must
be unique among all deployed composites.  The new service will overwrite the
old one.
        at
oracle.integration.platform.blocks.deploy.StandaloneCompositeDeploymentCoordin
atorImpl.coordinateCompositeDeployment(StandaloneCompositeDeploymentCoordinato
rImpl.java:99) 
. . .
. . .

This error occurred because all ADF bindings must have a unique service name across all deployed SOA composite applications.

As a workaround, you must edit the composite.xml file and assign a different name for the service in the.adf binding.adf section. For example:
```
<binding.adf serviceName="OrderProcessorService_v2" registryName=""/>
     
```