Jhs Lovs open new db connection

Question

We are using jheadstart 11.1.1.3.35. There is a need to minimise the database connections opened by the application. However we have noticed that all jhs LOVs in the application are opening a new database connection instead of using the db connection of the root application module. Is there any way to avoid this type of behaviour?
Thanks

Answer 1

Dear Steven,
I use the default configuration. Does it have to do that the development platform is linux, I doubt about it. In 5 applications using jheadstart 1.1.1.3.35 and jdeveloper 11.1.1.4.0, we encounter the same behaviour:
When we open a jhs lov for the first time a new connection spans. Then this connection is reused for any subsequent jhs lov calls.
So for every root application module with jhs lovs we always have 2 db connections (when we query v$session) instead of 1, so 5 root ams with jhs lovs will span 10 db connections.
I tried to change the transaction option to Always Use Existing Transaction but then a runtime exception is thrown:
Caused by: oracle.adf.controller.activity.ActivityLogicException: ADFC-00006: Existing transaction is required when calling task flow '/WEB-INF/adfc-config-EmployeesLookupn.xml#EmployeesLookupnTaskFlow'.
     at oracle.adfinternal.controller.activity.TaskFlowCallActivityLogic.validateModel(TaskFlowCallActivityLogic.java:908)
Also the "share data controls with calling task flow" option for the individual Lov is always checked by default. How can i change the data scope setting at the application level?
I can send you a small test case i created to see for yourself.
Thanks