-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Montag, 28. Januar 2013 17:45
To: dev@syncope.apache.org
Subject: Re: Console Resource User Mapping error
On 28/01/2013 17:41, Colm O hEigeartaigh wrote:
Apologies, for the noise, I've found
On 29/01/2013 11:31, Colm O hEigeartaigh wrote:
Thanks Jan! Fix confirmed. However I am running into a number of strange
problems still on trunk. I alluded to this problem earlier: I have a
Database Connector for a H2 backend with a simple table. I am creating a
Resource User Mapping of Username
Do you have such column GIVENNAME in the table configured for your H2
resource, right?
Yep.
This is normally happening because the admin console tries to populate
the external attribute name field, for non-AccountId
non-Password rows, by calling schema() on the underlying connector.
But the
Hi Francesco,
I am creating the new Connector from scratch + adding the new Resource.
Looking at core-rest.log I see the following:
16:24:39.799 DEBUG
org.apache.syncope.core.rest.controller.AbstractController - Resource
creation: org.apache.syncope.common.to.ResourceTO@1e2fce9c[
name=H2
On 28/01/2013 17:32, Colm O hEigeartaigh wrote:
Hi Francesco,
I am creating the new Connector from scratch + adding the new Resource.
Looking at core-rest.log I see the following:
[...]
Unless I am mistaken, it appears to be creating 5 mappings here?
a) Username - AccountId
b) Password -
Apologies, for the noise, I've found the error:
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:841)
at
org.apache.syncope.client.services.proxy.ResourceServiceProxy.create(ResourceServiceProxy.java:48)
at
On 28/01/2013 17:41, Colm O hEigeartaigh wrote:
Apologies, for the noise, I've found the error:
java.lang.IllegalArgumentException
at java.net.URI.create(URI.java:841)
at
org.apache.syncope.client.services.proxy.ResourceServiceProxy.create(ResourceServiceProxy.java:48)
Looks like it ;-)
It appears there is a second bug in that the ResourceModalPage is not
displaying errors properly, hence the Error:null display. I'll fix both.
Colm.
On Mon, Jan 28, 2013 at 4:45 PM, Francesco Chicchiriccò ilgro...@apache.org
wrote:
On 28/01/2013 17:41, Colm O hEigeartaigh
