You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2023/02/18 16:41:00 UTC
[jira] [Updated] (JCRVLT-690) Describe Session handling of Importer.run(....)
[ https://issues.apache.org/jira/browse/JCRVLT-690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated JCRVLT-690:
-----------------------------------
Description:
For edge cases where the session is
# containing already transient changes before calling {{Importer.run(...)}}
# supposed to be reused afterwards before committing finally atomically
it is important to know under which circumstances either {{Session.save()}} or {{Session.refresh(false)}} are executed on the given session within the Importer.
was:
For edge cases where the session is
# containing already transient changes before calling {{Importer.run(...)}}
# supposed to be reused afterwards before committing finally atomically
it is important to know under which circumstances either {{Session.save()}} or {{Session.refresh(true)}} are executed on the given session within the Importer.
> Describe Session handling of Importer.run(....)
> -----------------------------------------------
>
> Key: JCRVLT-690
> URL: https://issues.apache.org/jira/browse/JCRVLT-690
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
>
> For edge cases where the session is
> # containing already transient changes before calling {{Importer.run(...)}}
> # supposed to be reused afterwards before committing finally atomically
> it is important to know under which circumstances either {{Session.save()}} or {{Session.refresh(false)}} are executed on the given session within the Importer.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)