<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi,<br>
<br>
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.<br>
<br>
<pre class="moz-signature" cols="72">--
Radovan Semancik
Software Architect
evolveum.com
</pre>
<br>
<br>
On 09/27/2013 09:22 AM, Ivan Noris wrote:<br>
</div>
<blockquote cite="mid:52453237.3070903@evolveum.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Hi Vincent,<br>
<br>
<div class="moz-cite-prefix">On 09/26/2013 10:14 PM,
Belleville-Rioux, Vincent wrote:<br>
</div>
<blockquote
cite="mid:0AD36E0192997748BD28BC68B14C75D003620D@Lettre.gst.uqam.ca"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style type="text/css" id="owaParaStyle"></style>
<style type="text/css"></style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">
<div style="font-family:Tahoma; font-size:13px">Hi there, </div>
<div style="font-family:Tahoma; font-size:13px"><br>
</div>
<div style="font-family:Tahoma; font-size:13px">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?</div>
<div style="font-family:Tahoma; font-size:13px"><br>
</div>
</div>
</blockquote>
<br>
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.)<br>
<br>
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.<br>
<br>
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.)<br>
<br>
Regarding the <b>resourceRef</b> 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.<br>
<br>
Regards,<br>
Ivan<br>
<pre class="moz-signature" cols="72">--
Ing. Ivan Noris
Consultant
Evolveum, s.r.o
___________________________________________________
"Semper cautus - semper paratus - semper idem Vix."
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
midPoint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a>
<a class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>