[midPoint] Lookup Tables with attributes defined as xsd:int

[Ivan Noris]

Hi Chris,

I tried to replicate. And have a different error.

I created extension xsd:int, created a lookup table, attached to <item>
in object template.

The lookup values are displayed, but attempt to save end with:

2019-08-23 09:45:12,956 [] [pool-3-thread-1] ERROR
(com.evolveum.midpoint.web.component.progress.ProgressPanel): Error
executing changes.
com.evolveum.midpoint.util.exception.SystemException: Can't extract
value for saving from prism property value PPV(String:1) expected return
type class java.lang.Long, actua
l type class java.lang.String
        at
com.evolveum.midpoint.repo.sql.helpers.BaseHelper.handleGeneralRuntimeException(BaseHelper.java:173)
        at
com.evolveum.midpoint.repo.sql.helpers.BaseHelper.handleGeneralException(BaseHelper.java:153)
        at
com.evolveum.midpoint.repo.sql.helpers.ObjectUpdater.modifyObjectAttempt(ObjectUpdater.java:528)
        at
com.evolveum.midpoint.repo.sql.SqlRepositoryServiceImpl.modifyObject(SqlRepositoryServiceImpl.java:640)
        at
com.evolveum.midpoint.repo.cache.RepositoryCache.modifyObject(RepositoryCache.java:1069)
        at
com.evolveum.midpoint.model.impl.lens.ChangeExecutor.executeModification(ChangeExecutor.java:1539)
        at
com.evolveum.midpoint.model.impl.lens.ChangeExecutor.executeDelta(ChangeExecutor.java:954)
        at
com.evolveum.midpoint.model.impl.lens.ChangeExecutor.executeChanges(ChangeExecutor.java:201)
        at
com.evolveum.midpoint.model.impl.lens.Clockwork.lambda$processSecondary$0(Clockwork.java:801)
        at
com.evolveum.midpoint.model.impl.lens.ClockworkMedic.partialExecute(ClockworkMedic.java:217)
        at
com.evolveum.midpoint.model.impl.lens.ClockworkMedic.partialExecute(ClockworkMedic.java:163)
        at
com.evolveum.midpoint.model.impl.lens.Clockwork.processSecondary(Clockwork.java:799)
        at
com.evolveum.midpoint.model.impl.lens.Clockwork.click(Clockwork.java:623)
        at
com.evolveum.midpoint.model.impl.lens.Clockwork.run(Clockwork.java:209)
        at
com.evolveum.midpoint.model.impl.controller.ModelController.executeChanges(ModelController.java:565)
        at
com.evolveum.midpoint.web.component.progress.ProgressPanel$14.callWithContextPrepared(ProgressPanel.java:601)
        at
com.evolveum.midpoint.web.component.progress.ProgressPanel$14.callWithContextPrepared(ProgressPanel.java:587)
        at
com.evolveum.midpoint.web.component.SecurityContextAwareCallable.call(SecurityContextAwareCallable.java:59)
        at
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        at
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        at java.base/java.lang.Thread.run(Thread.java:834)

(no 500 internal server error though. This is master on Java 11)

So it looks that midPoint is not correctly assuming integer (long??) vs.
string...

I remember earlier issue: https://jira.evolveum.com/browse/MID-4506, but
that one was checked (by me) to work in March... Maybe a regression.

Please create a JIRA issue for your case if you need to use integer
lookup table values; and I will attach this also there.

Best regards,

Ivan

On 21. 8. 2019 15:13, Chris Woods wrote:
>
> Hi,
>
> is it possible that Lookup Tables can only be bound to attributes
> defined as xsd:string in a schema extension? I have one binding in the
> object template that works fine (xsd:string attribute) and another
> binding (xsd:int) that, when active, causes a 500 Internal Server
> Error when trying to edit a user.
>
> Can someone confirm this behaviour?
>
> Thanks in advance.
>
> Regards,
>
> Chris
>
>
>
> Content provided within this e-mail including any attachments, is for
> the use of the intended recipients and may contain Rohde & Schwarz
> company restricted information. Any unauthorized use, disclosure, or
> distribution of this communication in whole or in part is strictly
> prohibited. If you are not the intended recipient, please notify the
> sender by reply email or by telephone and delete the communication in
> its entirety.
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint

-- 
Ivan Noris
Senior Identity Engineer
evolveum.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20190823/3227f281/attachment.htm>