Hi,Can you help me on these issues what needs to be done to fix all
these violations. 1 & 2. Will these harm working of the components as
backward compatibility support is already there. And most of components
build on coral 2, and coral 2 is still supported in 6.5these similar
ones reportedly appear in PD report for so many components in migration
from 6.2 to 6.5 ,
MF dialog is showing intermittent behavior while adding MF option.The
very first time it works fine and after reload adding MF displays only
the delete button without the complete authoring field. (Figure below).
Looks like issue with coral library playing behind the scene.
Any way we can segregate libraries depending upon claasic/touch UII want
to keep both dialogs types in component, but the libraries (custom.js)
need to be seperately called in case of touch UI and other s when I open
dialog in classic.
Radio with MF does not seem to work with Coral2/Granite UI 1.0
either.Above link is not
Is it the known limitation? How does it work with custom.js
No, I dont want to update JCR and data source simultaneously, I want to
save all the JCR transactions once in the end, by utx.commit() if there
are no failure rates, and utx.rollback() in case of single failure. So I
think if anyway we can make use of JTA transactions, to store transient
data and submit and rollback as neededrepository =
JcrUtils.getRepository("http://localhost:4502/crx/server"); //Create a
Sessionjavax.jcr.Session session = repository.login( new