[midPoint] Custom Schema Extenstion

[Radovan Semancik]

Hi,

I have implemented it, it should work now. It is both in master and 
v2.2-support branches. It would be best for you to get a fresh build of 
v2.2-support branch. This is the code that will become v2.2.1 when 
enough bugfixes accumulate. To build this branch instead of master use 
your git tool to switch branches before building. Then build midPoint 
normally. If you are using reasonably recent command-line tools use the 
following commands:

git checkout --track v2.2-support

this needs to be done only first time you use the branch. After that you 
just use normal git checkout and pull commands. See 
https://wiki.evolveum.com/display/midPoint/Support+Branch for more details.

-- 

                                            Radovan Semancik
                                           Software Architect
                                              evolveum.com



On 09/18/2013 11:13 AM, Radovan Semancik wrote:
> Hi,
>
> Multiple schemas are supported. Just place more than file with xsd 
> extension in the schemas directory. However, there is catch. Only one 
> of the schemas may have annotation <a:extension ref="c:UserType"/>. 
> This is somehow implied by XSD principles. Therefore practically you 
> can have (only) one extension schema for user, one extension schema 
> for resource, etc.
>
> But now that I think about it ... it should be quite easy to merge 
> several complex type definitions into one. It would not be strictly 
> correct in XSD way, but it would be OK in midPoint/prism way (we have 
> unordered elements, Prism is designed to support this). And we are not 
> XSD fundamentalists anyway. I guess this would be a nice feature. We 
> will implement it. I have created a jira issues to track this:
> https://jira.evolveum.com/browse/MID-1600
>
> Thanks for the idea.
>