<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Vincent,<br>
<br>
and now I'm confused :-)<br>
<br>
The object template does not need to specify any assignment. For
example, our default "Default user template" specifies only
"Fullname" attribute (to be concatenated from Given name and Family
name attributes).<br>
<br>
In some customer setups however, we have mappings in object
templates, which are used to assign some
resources/roles/organizations - based on conditions.<br>
<br>
Can't tell what was wrong with your previous setup as I don't have
all of your objects.<br>
<br>
If you have any other issues, just ask and we will try to help you.<br>
<br>
Regards,<br>
Ivan<br>
<br>
<div class="moz-cite-prefix">On 09/27/2013 03:52 PM,
Belleville-Rioux, Vincent wrote:<br>
</div>
<blockquote
cite="mid:0AD36E0192997748BD28BC68B14C75D003635C@Lettre.gst.uqam.ca"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css"></style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">Actually I just found the problem. I
guess I didn't read the manual enough...
<div><br>
</div>
<div>What was happening is that I created a new Object Template
without putting the ResourceType assignment. I'm not entirely
sure why I need that mapping, but adding it to the Object
Template did fix the problem.</div>
<div><br>
</div>
<div>
<div> <c:mapping
xmlns:c=<a class="moz-txt-link-rfc2396E" href="http://midpoint.evolveum.com/xml/ns/public/common/common-2a">"http://midpoint.evolveum.com/xml/ns/public/common/common-2a"</a></div>
<div>
xmlns:icfs=<a class="moz-txt-link-rfc2396E" href="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-2">"http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/resource-schema-2"</a></div>
<div>
xmlns:t=<a class="moz-txt-link-rfc2396E" href="http://prism.evolveum.com/xml/ns/public/types-2">"http://prism.evolveum.com/xml/ns/public/types-2"</a></div>
<div>
xmlns:icfc=<a class="moz-txt-link-rfc2396E" href="http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/connector-schema-2">"http://midpoint.evolveum.com/xml/ns/public/connector/icf-1/connector-schema-2"</a></div>
<div>
xmlns:q=<a class="moz-txt-link-rfc2396E" href="http://prism.evolveum.com/xml/ns/public/query-2">"http://prism.evolveum.com/xml/ns/public/query-2"</a></div>
<div>
xmlns:cap=<a class="moz-txt-link-rfc2396E" href="http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-2">"http://midpoint.evolveum.com/xml/ns/public/resource/capabilities-2"</a></div>
<div>
xmlns:apti=<a class="moz-txt-link-rfc2396E" href="http://midpoint.evolveum.com/xml/ns/public/common/api-types-2">"http://midpoint.evolveum.com/xml/ns/public/common/api-types-2"</a></div>
<div>
xmlns:wfcf=<a class="moz-txt-link-rfc2396E" href="http://midpoint.evolveum.com/xml/ns/model/workflow/common-forms-2">"http://midpoint.evolveum.com/xml/ns/model/workflow/common-forms-2"</a></div>
<div>
xmlns:m=<a class="moz-txt-link-rfc2396E" href="http://midpoint.evolveum.com/xml/ns/public/model/model-context-2">"http://midpoint.evolveum.com/xml/ns/public/model/model-context-2"</a></div>
<div>
xmlns:ds=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2000/09/xmldsig#">"http://www.w3.org/2000/09/xmldsig#"</a></div>
<div>
xmlns:enc=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/04/xmlenc#">"http://www.w3.org/2001/04/xmlenc#"</a>></div>
<div> <c:expression></div>
<div> <c:value
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>></div>
<div> <c:assignment></div>
<div> <c:construction></div>
<div> <resourceRef
oid="00000000-0000-0000-0000-000000000008"
type="ResourceType"/></div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>
</c:construction></div>
<div><span class="Apple-tab-span" style="white-space:pre"></span>
</c:assignment></div>
<div> </c:value></div>
<div> </c:expression></div>
<div> <c:target></div>
<div> <c:path
xmlns:xsi=<a class="moz-txt-link-rfc2396E" href="http://www.w3.org/2001/XMLSchema-instance">"http://www.w3.org/2001/XMLSchema-instance"</a>>assignment</c:path></div>
<div> </c:target></div>
<div> </c:mapping></div>
<div><br>
</div>
<div>Vincent</div>
<div><br>
</div>
<div><br>
<div style="font-family: Times New Roman; color: #000000;
font-size: 16px">
<hr tabindex="-1">
<div id="divRpF781522" style="direction: ltr;"><font
color="#000000" size="2" face="Tahoma"><b>De :</b>
<a class="moz-txt-link-abbreviated" href="mailto:midpoint-bounces@lists.evolveum.com">midpoint-bounces@lists.evolveum.com</a>
[<a class="moz-txt-link-abbreviated" href="mailto:midpoint-bounces@lists.evolveum.com">midpoint-bounces@lists.evolveum.com</a>] de la part de
Radovan Semancik [<a class="moz-txt-link-abbreviated" href="mailto:radovan.semancik@evolveum.com">radovan.semancik@evolveum.com</a>]<br>
<b>Date d'envoi :</b> 27 septembre 2013 05:14<br>
<b>À :</b> <a class="moz-txt-link-abbreviated" href="mailto:midpoint@lists.evolveum.com">midpoint@lists.evolveum.com</a><br>
<b>Objet :</b> Re: [midPoint] Namespace problem<br>
</font><br>
</div>
<div>
<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 type="cite">Hi Vincent,<br>
<br>
<div class="moz-cite-prefix">On 09/26/2013 10:14 PM,
Belleville-Rioux, Vincent wrote:<br>
</div>
<blockquote type="cite">
<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" target="_blank"></fieldset>
<br>
<pre>_______________________________________________
midPoint mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com" target="_blank">midPoint@lists.evolveum.com</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint" target="_blank">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
<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>
<pre class="moz-signature" cols="72">--
Ing. Ivan Noris
Consultant
Evolveum, s.r.o
___________________________________________________
"Semper cautus - semper paratus - semper idem Vix."
</pre>
</body>
</html>