...
1. Use org.csstudio.platform.libs.epics plugin as one can access JCA directly.
2. Use org.csstudio.utility.pv.epics plugin so we can use any CSS apps.
3. Add the preferences "gov.aps.jca.jni.epics.linux-x86.library.path" and "gov.aps.jca.jni.epics.linux-x86.caRepeater.path" to the org.csstudio.platform.libs.epics plugin so it can use a different set of CA/JCA libraries outside CSS – we can then use our own copy of the CA/JCA native libraries. This is very important because we, at LCLS, may use a different version of EPICS/JCA. I believe many other accelerator facilities will be in the same situation.
4. We can then make XAL CA/JCA wrapper a plugin which depends on org.csstudio.platform.libs.epics, i.e. using the same jca.jar. This XAL JCA wrapper provides simpler APIs for channel access.
As all the above steps done, developers can have choice of all 3 ways to access JCA (1. directly, 2. via org.csstudio.utility.pv.epics, or 3. via XAL JCA wrapper plugin).
Conclusion and Priorities:
- We will initially use Kay's org.csstudio.utility.pv.epics to access EPICS PVs.
- We will execute steps 3 and 4 above to enable use to also use XAL's JCA wrapper.