Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.7K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
After ReDeploy/Deploy Auto Change URI of Task on Soa Server Issue

Hi,
I am using
JDeveloper 11.1.1.9
BPM Editor 11.1.1.9.0.1.7
Java 1.6.0_45
SOA Composite Editor 11.1.1.9.0.99.99
I have a bpm project. it has two different version on soa server.
For example:
first project version is 1.0
second project version is 2.0
I deployed first project to soa server and uri of this project version are like this : /workflow/v1.0/...................... on soa server
After I deploying second project (v2.0), this project tasks uri are /workflow/v2.0/...................... on soa server
After these deploys, I am checking first project (v1.0) again and this project version uri of tasks changed like this /workflow/v2.0/....
I mean uri of tasks changing when what I deployed latest same project.
Why uri of tasks changing, when I deployed a new version of bpm project?
Thanks.
Jack.
Best Answer
-
Pls dont change namespace.that ll meed lot of changes.
I would suggest going to EM post new deployment and change URI back to older one.
Sent from my iPhone
Answers
-
That's how it is .
Every UI Project has a file called hwtaskflow.xml which has an attribute called "TaskDefinitionNamespace"
so whenever a UI project is deployed, it goes to SOA-infra, finds out al the Human Tasks with same Name space and changes URI
Its a good feature from my prespective as when you have many versions and a new UI, it reflects on all HTs.
-
Hi @DurgadasHaldar,
Thanks for your answer.
I understood what you mean. So is there a way keep same uri without changing for it version of project
Because, I changed java class in adf project of bpm application. So new version workig different and if my users open old process instance with new uri, so they gets error.
All after deploy, I am changing uri for old version from soa server. In this way, old instance working with old uri, new version instance working with new uri.
I guess, I shouldn't change TaskDefinitionNamespace, or if I can change, how can do it?
Jack.
-
Pls dont change namespace.that ll meed lot of changes.
I would suggest going to EM post new deployment and change URI back to older one.
Sent from my iPhone
-
Hi,
Yes, you right.
I guess there isn't another way to solve this issue.
Thanks for helping @DurgadasHaldar.
Jack