You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@syncope.apache.org by Stéphane Popoff <st...@spopoff.net> on 2026/04/15 12:14:18 UTC
4.1.0 ProvisioningContext bean anyTypeClassDataBinder can't match constructor of AnyObjectDataBinderImpl
Hi,
I found that org.apache.syncope.core.provisioning.java.ProvisioningContext
Bean anyTypeClassDataBinder can't initialize the implementation of
AnyTypeClassDataBinder
(org.apache.syncope.core.provisioning.java.data.AnyTypeClassDataBinderImpl).
Because of a completely different signature.
This is part of a work on mine to connect a CORE to an Aura NEO4J persistence.
Best regards,
Stéphane POPOFF
Re: 4.1.0 ProvisioningContext bean anyTypeClassDataBinder can't match constructor of AnyObjectDataBinderImpl
Posted by Stéphane Popoff <st...@spopoff.net>.
You're right master was for the next version, that's my mistake.
Regards.
Le mer. 15 avr. 2026 à 17:13, Francesco Chicchiriccò
<il...@apache.org> a écrit :
>
> AnyChecker is not available in the branch 4_1_X nor in the 4.1.0 artifacts.
>
> It is instead available in the master branch:
>
> https://github.com/apache/syncope/blob/master/core/persistence-api/src/main/java/org/apache/syncope/core/persistence/api/dao/AnyChecker.java
>
> I think you should really clean up your dev environment.
>
> Regards.
>
> On 15/04/26 17:05, Stéphane Popoff wrote:
> > Hi Francesco,
> >
> > Sorry to get back, but with a complete new artifact project, when for
> > the CORE, I want to compile the ProvisioningContext.java (because of a
> > named Bean), it fails because of the lack in the Jar
> > (syncope-core-persistence-api-4.1.0.jar coming from the repo) of the
> > AnyChecker class.
> > What's wrong with the Jar in the repo ?
> >
> > Best regards,
> >
> > Stéphane POPOFF
> >
> > Le mer. 15 avr. 2026 à 16:16, Stéphane Popoff <st...@spopoff.net> a écrit :
> >> Hi Francesco,
> >>
> >> Your right, it's a mess with my NetBeans IDE.
> >> By the way it's hard to change the CORE persistence to Aura NEOJ
> >> because of the Beans naming.
> >>
> >> Best regards,
> >>
> >> Stéphane POPOFF
> >>
> >> Le mer. 15 avr. 2026 à 14:23, Francesco Chicchiriccò
> >> <il...@apache.org> a écrit :
> >>> Hi,
> >>> if this was true, how could Syncope 4.1.0 artifacts be built by the release process? And how could descendant projects work flawlessly ever since?
> >>>
> >>> I think you are mixing artifacts versions, you'd better check carefully.
> >>>
> >>> Regards.
> >>>
> >>> On 15/04/26 14:14, Stéphane Popoff wrote:
> >>>> Hi,
> >>>>
> >>>> I found that org.apache.syncope.core.provisioning.java.ProvisioningContext
> >>>> Bean anyTypeClassDataBinder can't initialize the implementation of
> >>>> AnyTypeClassDataBinder
> >>>> (org.apache.syncope.core.provisioning.java.data.AnyTypeClassDataBinderImpl).
> >>>> Because of a completely different signature.
> >>>>
> >>>> This is part of a work on mine to connect a CORE to an Aura NEO4J persistence.
> >>>>
> >>>> Best regards,
> >>>>
> >>>> Stéphane POPOFF
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Member at The Apache Software Foundation
> Syncope, Cocoon, Olingo, CXF, OpenJPA
> https://about.me/ilgrosso
>
Re: 4.1.0 ProvisioningContext bean anyTypeClassDataBinder can't match constructor of AnyObjectDataBinderImpl
Posted by Francesco Chicchiriccò <il...@apache.org>.
AnyChecker is not available in the branch 4_1_X nor in the 4.1.0 artifacts.
It is instead available in the master branch:
https://github.com/apache/syncope/blob/master/core/persistence-api/src/main/java/org/apache/syncope/core/persistence/api/dao/AnyChecker.java
I think you should really clean up your dev environment.
Regards.
On 15/04/26 17:05, Stéphane Popoff wrote:
> Hi Francesco,
>
> Sorry to get back, but with a complete new artifact project, when for
> the CORE, I want to compile the ProvisioningContext.java (because of a
> named Bean), it fails because of the lack in the Jar
> (syncope-core-persistence-api-4.1.0.jar coming from the repo) of the
> AnyChecker class.
> What's wrong with the Jar in the repo ?
>
> Best regards,
>
> Stéphane POPOFF
>
> Le mer. 15 avr. 2026 à 16:16, Stéphane Popoff <st...@spopoff.net> a écrit :
>> Hi Francesco,
>>
>> Your right, it's a mess with my NetBeans IDE.
>> By the way it's hard to change the CORE persistence to Aura NEOJ
>> because of the Beans naming.
>>
>> Best regards,
>>
>> Stéphane POPOFF
>>
>> Le mer. 15 avr. 2026 à 14:23, Francesco Chicchiriccò
>> <il...@apache.org> a écrit :
>>> Hi,
>>> if this was true, how could Syncope 4.1.0 artifacts be built by the release process? And how could descendant projects work flawlessly ever since?
>>>
>>> I think you are mixing artifacts versions, you'd better check carefully.
>>>
>>> Regards.
>>>
>>> On 15/04/26 14:14, Stéphane Popoff wrote:
>>>> Hi,
>>>>
>>>> I found that org.apache.syncope.core.provisioning.java.ProvisioningContext
>>>> Bean anyTypeClassDataBinder can't initialize the implementation of
>>>> AnyTypeClassDataBinder
>>>> (org.apache.syncope.core.provisioning.java.data.AnyTypeClassDataBinderImpl).
>>>> Because of a completely different signature.
>>>>
>>>> This is part of a work on mine to connect a CORE to an Aura NEO4J persistence.
>>>>
>>>> Best regards,
>>>>
>>>> Stéphane POPOFF
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA
https://about.me/ilgrosso
Re: 4.1.0 ProvisioningContext bean anyTypeClassDataBinder can't match constructor of AnyObjectDataBinderImpl
Posted by Stéphane Popoff <st...@spopoff.net>.
Hi Francesco,
Sorry to get back, but with a complete new artifact project, when for
the CORE, I want to compile the ProvisioningContext.java (because of a
named Bean), it fails because of the lack in the Jar
(syncope-core-persistence-api-4.1.0.jar coming from the repo) of the
AnyChecker class.
What's wrong with the Jar in the repo ?
Best regards,
Stéphane POPOFF
Le mer. 15 avr. 2026 à 16:16, Stéphane Popoff <st...@spopoff.net> a écrit :
>
> Hi Francesco,
>
> Your right, it's a mess with my NetBeans IDE.
> By the way it's hard to change the CORE persistence to Aura NEOJ
> because of the Beans naming.
>
> Best regards,
>
> Stéphane POPOFF
>
> Le mer. 15 avr. 2026 à 14:23, Francesco Chicchiriccò
> <il...@apache.org> a écrit :
> >
> > Hi,
> > if this was true, how could Syncope 4.1.0 artifacts be built by the release process? And how could descendant projects work flawlessly ever since?
> >
> > I think you are mixing artifacts versions, you'd better check carefully.
> >
> > Regards.
> >
> > On 15/04/26 14:14, Stéphane Popoff wrote:
> > > Hi,
> > >
> > > I found that org.apache.syncope.core.provisioning.java.ProvisioningContext
> > > Bean anyTypeClassDataBinder can't initialize the implementation of
> > > AnyTypeClassDataBinder
> > > (org.apache.syncope.core.provisioning.java.data.AnyTypeClassDataBinderImpl).
> > > Because of a completely different signature.
> > >
> > > This is part of a work on mine to connect a CORE to an Aura NEO4J persistence.
> > >
> > > Best regards,
> > >
> > > Stéphane POPOFF
> >
> > --
> > Francesco Chicchiriccò
> >
> > Tirasa - Open Source Excellence
> > http://www.tirasa.net/
> >
> > Member at The Apache Software Foundation
> > Syncope, Cocoon, Olingo, CXF, OpenJPA
> > https://about.me/ilgrosso
> >
Re: 4.1.0 ProvisioningContext bean anyTypeClassDataBinder can't match constructor of AnyObjectDataBinderImpl
Posted by Stéphane Popoff <st...@spopoff.net>.
Hi Francesco,
Your right, it's a mess with my NetBeans IDE.
By the way it's hard to change the CORE persistence to Aura NEOJ
because of the Beans naming.
Best regards,
Stéphane POPOFF
Le mer. 15 avr. 2026 à 14:23, Francesco Chicchiriccò
<il...@apache.org> a écrit :
>
> Hi,
> if this was true, how could Syncope 4.1.0 artifacts be built by the release process? And how could descendant projects work flawlessly ever since?
>
> I think you are mixing artifacts versions, you'd better check carefully.
>
> Regards.
>
> On 15/04/26 14:14, Stéphane Popoff wrote:
> > Hi,
> >
> > I found that org.apache.syncope.core.provisioning.java.ProvisioningContext
> > Bean anyTypeClassDataBinder can't initialize the implementation of
> > AnyTypeClassDataBinder
> > (org.apache.syncope.core.provisioning.java.data.AnyTypeClassDataBinderImpl).
> > Because of a completely different signature.
> >
> > This is part of a work on mine to connect a CORE to an Aura NEO4J persistence.
> >
> > Best regards,
> >
> > Stéphane POPOFF
>
> --
> Francesco Chicchiriccò
>
> Tirasa - Open Source Excellence
> http://www.tirasa.net/
>
> Member at The Apache Software Foundation
> Syncope, Cocoon, Olingo, CXF, OpenJPA
> https://about.me/ilgrosso
>
Re: 4.1.0 ProvisioningContext bean anyTypeClassDataBinder can't match constructor of AnyObjectDataBinderImpl
Posted by Francesco Chicchiriccò <il...@apache.org>.
Hi,
if this was true, how could Syncope 4.1.0 artifacts be built by the release process? And how could descendant projects work flawlessly ever since?
I think you are mixing artifacts versions, you'd better check carefully.
Regards.
On 15/04/26 14:14, Stéphane Popoff wrote:
> Hi,
>
> I found that org.apache.syncope.core.provisioning.java.ProvisioningContext
> Bean anyTypeClassDataBinder can't initialize the implementation of
> AnyTypeClassDataBinder
> (org.apache.syncope.core.provisioning.java.data.AnyTypeClassDataBinderImpl).
> Because of a completely different signature.
>
> This is part of a work on mine to connect a CORE to an Aura NEO4J persistence.
>
> Best regards,
>
> Stéphane POPOFF
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA
https://about.me/ilgrosso