Hi, Lorenzo! Some follow up questions.
>and in general for increase performance I can
suggest you to not use the CSVDIR as a connector. This connector is not
the best one in order to have a performing environment
What do you recommend? (It would be nice if we could produce output in XML)
P.S.
sorry, I missed the link :)
[4] https://syncope.apache.org/docs/2.1/getting-started#maven-project
Il 31/07/19 14:18, Andrea Patricelli ha scritto:
Syncope docker images are harder to customize respect to the simple
java artifacts generated with the "preferred method" for installation
Syncope docker images are harder to customize respect to the simple java
artifacts generated with the "preferred method" for installation [4].
For this reason if you want to customize Syncope though Java classes, I
suggest to you to get Syncope from archetype and deploy wars on your
preferred
We were able to get the class created but we are still struggling with
finding where org.apache.syncope.core.provisioning.java.data is properly
located within the docker instance.
Some help would be greatly appreciated
thanks,
-Noah
On Tue, Jul 30, 2019 at 10:45 AM Andrea Patricelli <
Hi Lynn,
please read in line.
Il 29/07/19 23:58, lfinch ha scritto:
Hello - I'm running a 2.1.2 implementation and have 9 plain schema defined.
I'm using CSVDIR as connector. Pull task is set to full recon,
matching=update, unmatching = provision (create/update/sync). Push task is
also
