1 person found this helpful
I just tested on my JDev 188.8.131.52 with both SOA Composite and BPMN editor versions 184.108.40.206.0.00.97 against SOA 220.127.116.11.3 (18072286 ) and it works.
Looking the KM I found an internal article describing a problem similar to yours on 18.104.22.168.0 that was fixed by updating the JDev SOA composite
So the recommendation is to update the SOA Composite and BPMN editor on JDev and possibly install the BP4 (latest bundle patch) on the SOA runtime
Thanks a lot for the suggestion.
My development environment is as following:
- JDeveloper Studio Edition Version 22.214.171.124.0
- BPMN Editor v126.96.36.199.0.0.97
- SOA Composite Editor v188.8.131.52.0.00.97
- SOA Suite 184.108.40.206.0
After reading your reply, I tried to update my BPM Editor and SOA Composite Editor extensions. The current version are:
- BPMN Editor v220.127.116.11.0.1.32
- SOA Composite Editor v18.104.22.168.0.01.32
Unfortunately, the updates couldn't solve the problem .
I'm sure Gabriel's onto something, but I've noticed the same problem.
Might not be your issue, but I find that I can get it to work if JDeveloper is running on the same machine as the server. For example when using a VM, and I try running JDeveloper to expose protected flex fields it will not work. When I run JDeveloper on the VM then it works fine.
Not a great solution I know, but that's been the only way I've gotten it to work in 22.214.171.124.
Currently, I'm using a stand-alone WLS on my laptop for development. So, this problem happens even with JDeveloper on the same machine.
After updating BPM Editor and SOA Composite Editor extensions to the latest version via JDeveloper, I noticed that the SOA server throwed the following exception in the log every time I tried to access the Attribute drop-down menu:
Invalid Token Error in Verification Service. Received invalid token in null. Verify that correct token is passed. ORABPEL-30503 Invalid Token Error in Verification Service. Invalid Token Error in Verification Service. Received invalid token in null. Verify that correct token is passed. ... Caused by: java.lang.Exception: Null token ...
The above exception is indeed caused by SOA Suite v126.96.36.199.0. After applying the SOA Bundle Patch v188.8.131.52.4, the issue is finally resolved. JDeveloper can now show the Attribute list for mapping.