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ò <[email protected] > wrote: > 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) >> at >> org.apache.syncope.console.**rest.ResourceRestClient.** >> create(ResourceRestClient.**java:65) >> >> ... >> >> Caused by: java.net.URISyntaxException: Illegal character in path at index >> 51: >> http://localhost:9080/syncope/**rest/resource/read/H2<http://localhost:9080/syncope/rest/resource/read/H2>Resource.json >> at java.net.URI$Parser.fail(URI.**java:2810) >> >> It can't handle a space in the name of the Resource. >> > > Are we just missing a good old URLEncoder.encode() in > ConnectorRestClient,java on console side? > > Regards. > > On Mon, Jan 28, 2013 at 4:37 PM, Francesco Chicchiriccò < >> [email protected] >> >>> wrote: >>> 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 -> Password >>>> c) surname -> SURNAME >>>> >>>> and the extra: >>>> >>>> d) Username -> AccountId (with extAttrName=__NAME__) >>>> e) Password -> Password (with extAttrName=__PASSWORD__) >>>> >>>> That's wrong, it seems like (d) and (e) are some sort of "preliminary" >>> version of (a) and (b). >>> >>> Anyway, this should generate an error for "invalid mapping", since there >>> must be exactly a single AccountId per resource (and user / role). >>> >>> Is this reported in the logs? Is the mapping created on the core? >>> >>> Regards. >>> >>> On Mon, Jan 28, 2013 at 4:13 PM, Francesco Chicchiriccò < >>> >>>> [email protected] >>>> >>>> wrote: >>>>> On 28/01/2013 16:48, Colm O hEigeartaigh wrote: >>>>> >>>>> Hi guys, >>>>> >>>>>> I'm getting a strange error when adding some Resource User Mappings in >>>>>> the >>>>>> Console on trunk. I have a H2 backend, and I configure a Connector for >>>>>> it. >>>>>> I am adding a Username/Password/User Schema attribute mapping. When I >>>>>> try >>>>>> to save it, I see an "Error:null" on the top of the screen + the >>>>>> following >>>>>> error in the logs: >>>>>> >>>>>> 15:43:51.031 ERROR org.apache.syncope.console.***** >>>>>> *pages.AbstractBasePage >>>>>> - >>>>>> Failure managing resource org.apache.syncope.common.to.****** >>>>>> >>>>>> >>>>>> ResourceTO@d0bbe47..... >>>>>> >>>>>> The weird thing is when I cancel the Resource creation it still >>>>>> appears >>>>>> in >>>>>> the table, and when I edit it again and look at the User mappings, I >>>>>> see >>>>>> that the Username + Password (AccountId + Password) mappings show up >>>>>> with >>>>>> an external attribute configured from the table in the backend. >>>>>> >>>>>> Can someone confirm this is a bug? >>>>>> >>>>>> At least it smells like that :-) >>>>>> >>>>> You should take a deeper log to both console's and core's logs to >>>>> understand what's happening. >>>>> >>>>> Are you creating the H2 connector in the same session as the associated >>>>> resource or is the connector pre-existing? My guess is that the >>>>> schema() >>>>> call on the connector is failing for some reason. >>>>> >>>>> Regards. >>>>> >>>> > -- > Francesco Chicchiriccò > > ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member > http://people.apache.org/~**ilgrosso/<http://people.apache.org/~ilgrosso/> > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
