Version numbers incorrectly assigned - currently uses an auto-increment approach rather than using the number associated with the deployment

When a single BPEL process is deployed, the version number matches the increment.

However if a second BPEL process is deployed, its version will continue from where the last version number of the first process left off, rather than using the number explicitly associated with the deployment.