Thought I'd give M4 a spin.
One connector, one resource, one pull task. With only user-mapping
everything is fine. But if also adding a group mapping (on the same
connector, resource and pull task ) I get some firework.
This puzzles me " *The field "realm" of instance
"JPAGroup[f873e8f2-3556-4c14-b3e8-f235567c14fd]" contained a null value;*"
Should not that value come from the pull task (Destination Realm) ?
Anything changed from M3 ? I have not (yet) touched/enabled realm
provisioning.
11:06:03.841 ERROR org.apache.syncope.core.provisioning.java.job.TaskJob
- While executing task 0c93de5b-9e5d-43d8-93de-5b9e5d83d8f2
org.springframework.dao.InvalidDataAccessApiUsageException: The field
"realm" of instance "JPAGroup[f873e8f2-3556-4c14-b3e8-f235567c14fd]"
contained a null value; the metadata for this field specifies that nulls
are illegal.; nested exception is <openjpa-2.4.1-r422266:1730418 fatal
user error> org.apache.openjpa.persistence.InvalidStateException: The
field "realm" of instance
"JPAGroup[f873e8f2-3556-4c14-b3e8-f235567c14fd]" contained a null value;
the metadata for this field specifies that nulls are illegal.
at
org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:381)
~[spring-orm-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:122)
~[spring-orm-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.dao.support.DataAccessUtils.translateIfNecessary(DataAccessUtils.java:213)
~[spring-tx-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:530)
~[spring-orm-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:761)
~[spring-tx-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:730)
~[spring-tx-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:485)
~[spring-tx-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:291)
~[spring-tx-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
~[spring-tx-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.apache.syncope.core.persistence.jpa.spring.DomainTransactionInterceptor.invoke(DomainTransactionInterceptor.java:64)
~[syncope-core-persistence-jpa-2.0.0-M4.jar:2.0.0-M4]
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
~[spring-aop-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
~[spring-aop-4.3.0.RELEASE.jar:4.3.0.RELEASE]
at com.sun.proxy.$Proxy348.execute(Unknown Source) ~[?:?]
at
org.apache.syncope.core.provisioning.java.job.TaskJob$1.exec(TaskJob.java:80)
~[syncope-core-provisioning-java-2.0.0-M4.jar:2.0.0-M4]
at
org.apache.syncope.core.provisioning.java.job.TaskJob$1.exec(TaskJob.java:70)
~[syncope-core-provisioning-java-2.0.0-M4.jar:2.0.0-M4]
at
org.apache.syncope.core.spring.security.AuthContextUtils.execWithAuthContext(AuthContextUtils.java:114)
~[syncope-core-spring-2.0.0-M4.jar:2.0.0-M4]
at
org.apache.syncope.core.provisioning.java.job.TaskJob.execute(TaskJob.java:69)
~[syncope-core-provisioning-java-2.0.0-M4.jar:2.0.0-M4]
at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
~[quartz-2.2.3.jar:?]
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573)
~[quartz-2.2.3.jar:?]
Caused by: org.apache.openjpa.persistence.InvalidStateException: The
field "realm" of instance "JPAGroup[f873e8f2-3556-4c14-b3e8-f2355
