There are two different things:
The ConnID jar file, that file is responsible for connecting syncope to a
database. This jar should be in the bundles directory
The JDBC connector jar. That is responsible for connecting a java
application (any java application) to a specific database, for example
Thank you Francesco. If you need additional logging or any other info, just
ask
Jesse
On Thu, Feb 21, 2013 at 5:28 PM, Francesco Chicchiriccò ilgro...@apache.org
wrote:
On 21/02/2013 09:11, Jesse van Bekkum wrote:
Hi
Our syncope installation has recently crashed a lot (in the end
. In the past (0.7) we have
used manual propagation, by retrieving the propagation handler from the
context and firing it, but that seems a bit inelegant to me.
What is the preferred solution to this (I think common) scenario?
Jesse van Bekkum
:
On 30/04/2013 10:21, Jesse van Bekkum wrote:
No, I was just reading the requirements. I will get to it, but I will also
need permission from Everett. The complete procedure will probably take a
while I see.
Ok, let's wait for that.
Regards.
On Tue, Apr 30, 2013 at 10:15 AM
reliably?)
The only way I can get it to work is to do a rest call from the workflow,
but this is a hack, and unreliable
Jesse
On Tue, May 21, 2013 at 11:29 AM, Jesse van Bekkum bek...@gmail.com wrote:
I am not trying an update to an external resource, I am trying a
provisioning
a solution I'll post it.
Jesse
On Thu, May 30, 2013 at 3:21 PM, Fabio Martelli fabio.marte...@gmail.comwrote:
Il 28/05/2013 11:17, Jesse van Bekkum ha scritto:
Hi
I looked in to it yesterday evening, and this is an example on how to
reproduce this issue on a blank syncope installation.
I did
examples. I tried to assign the role name, but that did not
work.
With kind regards
Jesse van Bekkum
iWelcome
