[midPoint] Custom schema extension help

[Tys Remi]

Hi,

Good to hear that it's been changed.

I managed to figure out the attribute mapping problem as well.
The thing was that I didn't really realize the resource object had been transformed so I didn't have the <objects > anymore. When creating a fresh resource object I put the ns in the <objects> and it automatically added it as it should.
I also managed to solve it earlier in a poorer way by defining the ns in the path itself but that's not necessary if you put it in from the get-go.

Remi
________________________________________
From: midpoint-bounces at lists.evolveum.com [midpoint-bounces at lists.evolveum.com] on behalf of Ivan Noris [ivan.noris at evolveum.com]
Sent: 30 May 2013 17:17
To: midPoint General Discussion
Subject: Re: [midPoint] Custom schema extension help

Hi again,

> After comparing the the content with what was on the wiki I found that the sample on page https://wiki.evolveum.com/display/midPoint/Custom+Schema+Extension has an old/faulty "c" namespace. It should be common-2a instead of common-2.
> This should be changed.
>
> https://wiki.evolveum.com/dosearchsite.action?queryString=common-2 shows that there are a few more pages with the namespace.

FYI the common-2 bug in wiki has been resolved recently
(https://jira.evolveum.com/browse/MID-1359).

Ivan

--
   Ing. Ivan Noris
   Consultant
   Evolveum, s.r.o
   ___________________________________________________
   "Semper cautus - semper paratus - semper idem Vix."

_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint