[midPoint] Namespace problem

[Radovan Semancik]

Hi,

Ivan is right. It is most likely XML prefixes. These got destroyed by 
the XML libraries quite often. There is no practical way how to fix it 
now so the way that Ivan recommends is perhaps the best one. This is one 
of the "nuances" of XML and XML libraries that we need to live with. For 
now. I do not want to go deep into the philosophy of why we really want 
QNames but why XML is making that painful. To make the long story short: 
we are looking into a practical way how to support also JSON in a very 
near future. The JSON way may be much more comfortable for some people. 
The architecture allows JSON support to be introduced quite easily. We 
just need to figure out few practical issues and as the devil is in the 
detail this may take some time. So for now we need to live with XML. At 
least for a while.

-- 

                                            Radovan Semancik
                                           Software Architect
                                              evolveum.com



On 09/27/2013 09:22 AM, Ivan Noris wrote:
> Hi Vincent,
>
> On 09/26/2013 10:14 PM, Belleville-Rioux, Vincent wrote:
>> Hi there,
>>
>> Anyone of you have any idea why I get a namespace problem when trying 
>> to import objects from a CSV file and sending them to a specific 
>> obect template?
>>
>
> I suppose that both of your problems may be related to that strange 
> generated xml prefixes. (The reason why they are generated would be 
> better explained by some of my coleagues in the core team.)
>
> I recommend to always create, maintain and edit the XML files on disk, 
> make all of your modifications there, and import using either Import 
> from file or Import from embedded editor (via copy & paste). To create 
> the XML files I highly recommend to use our samples 
> (samples/resources/...) until the resource wizard is finished. This 
> way you can also put your files to CSV, svn, git etc. We do it in our 
> customer projects.
>
> Do you have the files stored on disk? Does the problem occur when 
> (re)importing them? Do you have the strange generated prefixes in your 
> files as well? (I see gen914 in your synchronization fragment of your 
> resource configuration.)
>
> Regarding the *resourceRef* problem - are you perhaps using some 
> assignments/roles in the object template? The assignments do reference 
> resources using resourceRef elements, the namespace problem could be 
> there.
>
> Regards,
> 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


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