On 04/22/2015 04:48 PM, Steve Moyer wrote:
I can provide a bit more detail on Igloo but bear in mind that I believe it needs rework too. We required the intermediate system to do much more than map attributes between JSON and persistence due to our business requirements. We accomplished this by creating JAXB annotated classes for each type of SCIM resource and letting JAX-RS unmarshall the received JSON into an associated Java object.
Just a curious question: how do you handle the dynamic schema extensions that SCIM has? These are dynamic parts, not available on compile-time so by definition they cannot be processes by JAXB.
We had a similar issue back in 2011-2012 while developing midPoint. We had also based the solution on JAXB. But we have found that pure JAXB is almost useless in such situations. We had to completely rework that data representation under the JAXB layer, dramatically extend the code generator and do lots of other things to make the dynamic part work reasonably well. It was a work for more than 2 years. It works quite well now, but there are still some incomplete parts ...
So I wonder whether you happened to find any easier solution that we have missed?
-- Radovan Semancik Software Architect evolveum.com
