RE: Console Resource User Mapping error

2013-01-29 Thread Jan Bernhardt 
 -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 the error:
 
  java.lang.IllegalArgumentException
   at java.net.URI.create(URI.java:841)
   at
 
 org.apache.syncope.client.services.proxy.ResourceServiceProxy.create(Reso
 urceServiceProxy.java:48)
   at
  org.apache.syncope.console.rest.ResourceRestClient.create(ResourceRest
  Client.java:65)
 
  ...
 
  Caused by: java.net.URISyntaxException: Illegal character in path at
  index
  51: 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?

Ups. This must have been me. 
I'll fix ServiceProxies. Discovered that same applies to 
ConfigurationServiceProxy and SchemaServiceProxy.

Reagrds.
Jan

 
 Regards.
 
  On Mon, Jan 28, 2013 at 4:37 PM, Francesco Chicchiriccò
  ilgro...@apache.org
  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ò 
  ilgro...@apache.org
 
  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/

Re: [Question] Problem with test UsertTestITCase.issueSYNCOPE279

2013-01-29 Thread Fabio Martelli 

Il giorno 28/gen/2013, alle ore 18.54, Andrei Shakirin ha scritto:

 Hi Fabio,
 
 Investigated a little bit more and found the following:
 
 1. TimeoutException
 This is the expected exception: it should be handled and returned as a
 SyncopeClientErrorException.
 
 Not really. As far as I can see TimeoutException thrown by 
 ConnectorFacadeProxy.getObject() is never wrapped to 
 SyncopeClientErrorException.
 Check the whole chain: UserController.create() - 
 UserController.createInternal() - taskExecutor.execute() - 
 PriorityPropagationTaskExecutor.execute() - 
 AbstractPropagationTaskExecutor.getRemoteObject() - 
 ConnectorFacadeProxy.getObject();
 
 AbstractPropagationTaskExecutor.getRemoteObject() just re-throws the Timeout 
 exception.
 syncopeClientError.jsp doesn't handle the TimeoutException and returns 
 InternalServerError that I get from my test.

Hi Andrei, I found the problem: into the AbstractPropagationTaskExecutor, line 
334, the call to getRemoteObject have to be encapsulated into a try-catch body.
As you can see, this is not an issue related to the TimeoutException only but 
it is an issue of the whole propagation process.

TimeoutException (or whatever specific propagation exception) won't be never 
thrown ...

Let me take care of this particular fix.

 That explains why this test doesn't work. Why it works during the build? - 
 see topic (2)
 
 2. Why UserTestITCase. issueSYNCOPE279() works sometimes.
 If UserTestITCase executed after some previous tests (or under some other 
 conditions: JDK, OS, etc), it throws other exception BEFORE execute the task:

This is terrible: why the creation of a new virtual attribute should fail?  
Doesn't UVirAttr id auto generation work fine anymore?
Can you investigate more?

 18:23:41.946 ERROR org.apache.syncope.core.rest.controller.AbstractController 
 - Exception thrown by REST methods
 org.springframework.dao.DataIntegrityViolationException: The transaction has 
 been rolled back.  See the nested exceptions for details on the errors that 
 occurred.; nested exception is openjpa-2.2.1-r422266:1396819 fatal store 
 error org.apache.openjpa.persistence.EntityExistsException: The transaction 
 has been rolled back.  See the nested exceptions for details on the errors 
 that occurred.
 FailedObject: org.apache.syncope.core.persistence.beans.user.UVirAttr@cd0cca3
   at 
 org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessExceptionIfPossible(EntityManagerFactoryUtils.java:313)
  ~[spring-orm-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible(DefaultJpaDialect.java:121)
  ~[spring-orm-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:517)
  ~[spring-orm-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:755)
  ~[spring-tx-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:724)
  ~[spring-tx-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.transaction.interceptor.TransactionAspectSupport.commitTransactionAfterReturning(TransactionAspectSupport.java:387)
  ~[spring-tx-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:120)
  ~[spring-tx-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
  ~[spring-aop-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at 
 org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
  ~[spring-aop-3.2.1.RELEASE.jar:3.2.1.RELEASE]
   at $Proxy137.create(Unknown Source) ~[na:na]
   at 
 org.apache.syncope.core.rest.controller.UserController.createInternal(UserController.java:306)
  ~[UserController.class:na]
   at 
 org.apache.syncope.core.rest.controller.UserController.create(UserController.java:284)
  ~[UserController.class:na]
 
 Caused by: org.apache.openjpa.persistence.EntityExistsException: Eindeutiger 
 Index oder Primärschlüssel verletzt: PRIMARY_KEY_C4 ON PUBLIC.UVIRATTR(ID)
 Unique index or primary key violation: PRIMARY_KEY_C4 ON 
 PUBLIC.UVIRATTR(ID); SQL statement:
 INSERT INTO PUBLIC.UVirAttr (ID, OWNER_ID, VIRTUALSCHEMA_NAME) VALUES (?, ?, 
 ?) [23505-170] {prepstmnt 2122205967 INSERT INTO PUBLIC.UVirAttr (ID, 
 OWNER_ID, VIRTUALSCHEMA_NAME) VALUES (?, ?, ?)} [code=23505, state=23505]
 
 DataIntegrityViolationException is mapped to SyncopeClientCompositeError Type 
 header in syncopeClientError.jsp and interpreted as SCCEE on the client side. 
 Test is green just because this effect.
 I think the reason of this DataIntegrityViolationException is AUTO generation

Re: [Question] Problem with test UsertTestITCase.issueSYNCOPE279

2013-01-29 Thread Fabio Martelli 

Il giorno 29/gen/2013, alle ore 10.10, Andrei Shakirin ha scritto:

 Hi Fabio,
 
 Hi Andrei, I found the problem: into the AbstractPropagationTaskExecutor,
 line 334, the call to getRemoteObject have to be encapsulated into a try-
 catch body.
 As you can see, this is not an issue related to the TimeoutException only but
 it is an issue of the whole propagation process.
 
 OK, sounds reasonable. Propagation exceptions should be wrapped on high level 
 exception like SCCEE.
 Just curious how this test runs by you before? Is there the same reason as in 
 my topic (2)?

Really I don't know. Probably (2) is the main reason.

 
 This is terrible: why the creation of a new virtual attribute should fail?
 Doesn't UVirAttr id auto generation work fine anymore?
 Can you investigate more?
 
 I already have seen the same effect with Notification DAO object: discussion 
 http://mail-archives.apache.org/mod_mbox/syncope-dev/201301.mbox/%3c50f3c43f.1000...@apache.org%3E
  .
 It seems that AUTO generation strategy doesn't work properly under high 
 volume/ high concurrency at least for H2 DB.
 
 Currently I see only one reliable way to avoid it: use TABLE based ID 
 strategy for all objects.
 WDYT?

A little overhead during the development phase but stronger in fact.
I can agree.

Regards,
F.

 Regards,
 Andrei.
 
 -Original Message-
 From: Fabio Martelli [mailto:fabio.marte...@gmail.com]
 Sent: Dienstag, 29. Januar 2013 09:40
 To: Andrei Shakirin
 Cc: dev@syncope.apache.org
 Subject: Re: [Question] Problem with test UsertTestITCase.issueSYNCOPE279
 
 
 Il giorno 28/gen/2013, alle ore 18.54, Andrei Shakirin ha scritto:
 
 Hi Fabio,
 
 Investigated a little bit more and found the following:
 
 1. TimeoutException
 This is the expected exception: it should be handled and returned as
 a SyncopeClientErrorException.
 
 Not really. As far as I can see TimeoutException thrown by
 ConnectorFacadeProxy.getObject() is never wrapped to
 SyncopeClientErrorException.
 Check the whole chain: UserController.create() -
 UserController.createInternal() - taskExecutor.execute() -
 PriorityPropagationTaskExecutor.execute() -
 AbstractPropagationTaskExecutor.getRemoteObject() -
 ConnectorFacadeProxy.getObject();
 
 AbstractPropagationTaskExecutor.getRemoteObject() just re-throws the
 Timeout exception.
 syncopeClientError.jsp doesn't handle the TimeoutException and returns
 InternalServerError that I get from my test.
 
 Hi Andrei, I found the problem: into the AbstractPropagationTaskExecutor,
 line 334, the call to getRemoteObject have to be encapsulated into a try-
 catch body.
 As you can see, this is not an issue related to the TimeoutException only but
 it is an issue of the whole propagation process.
 
 TimeoutException (or whatever specific propagation exception) won't be
 never thrown ...
 
 Let me take care of this particular fix.
 
 That explains why this test doesn't work. Why it works during the
 build? - see topic (2)
 
 2. Why UserTestITCase. issueSYNCOPE279() works sometimes.
If UserTestITCase executed after some previous tests (or under some
 other conditions: JDK, OS, etc), it throws other exception BEFORE execute
 the task:
 
 This is terrible: why the creation of a new virtual attribute should fail?
 Doesn't UVirAttr id auto generation work fine anymore?
 Can you investigate more?
 
 18:23:41.946 ERROR
 org.apache.syncope.core.rest.controller.AbstractController - Exception
 thrown by REST methods
 org.springframework.dao.DataIntegrityViolationException: The transaction
 has been rolled back.  See the nested exceptions for details on the errors
 that occurred.; nested exception is openjpa-2.2.1-r422266:1396819 fatal
 store error org.apache.openjpa.persistence.EntityExistsException: The
 transaction has been rolled back.  See the nested exceptions for details on
 the errors that occurred.
 FailedObject:
 org.apache.syncope.core.persistence.beans.user.UVirAttr@cd0cca3
 at
 org.springframework.orm.jpa.EntityManagerFactoryUtils.convertJpaAccessE
 xceptionIfPossible(EntityManagerFactoryUtils.java:313) ~[spring-orm-
 3.2.1.RELEASE.jar:3.2.1.RELEASE]
 at
 org.springframework.orm.jpa.DefaultJpaDialect.translateExceptionIfPossible
 (DefaultJpaDialect.java:121) ~[spring-orm-3.2.1.RELEASE.jar:3.2.1.RELEASE]
 at
 org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransac
 tionManager.java:517) ~[spring-orm-3.2.1.RELEASE.jar:3.2.1.RELEASE]
 at
 org.springframework.transaction.support.AbstractPlatformTransactionMana
 ger.processCommit(AbstractPlatformTransactionManager.java:755) ~[spring-
 tx-3.2.1.RELEASE.jar:3.2.1.RELEASE]
 at
 org.springframework.transaction.support.AbstractPlatformTransactionMana
 ger.commit(AbstractPlatformTransactionManager.java:724) ~[spring-tx-
 3.2.1.RELEASE.jar:3.2.1.RELEASE]
 at
 org.springframework.transaction.interceptor.TransactionAspectSupport.com
 mitTransactionAfterReturning(TransactionAspectSupport.java:387) ~[spring-

[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Replace Spring Webservice Stack with Apache CXF)

2013-01-29 Thread Andrei Shakirin (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565221#comment-13565221
 ] 

Andrei Shakirin commented on SYNCOPE-231:
-

Andrei,
any news about the errors with JDK 1.7?

Hi Francesco,
It seems that I have found the reason: see discussion [Question] Problem with 
test UsertTestITCase.issueSYNCOPE279.
I will test it additionally after the Fabio fix.
Problem with AUTO generation strategy scares me a little bit - sometimes errors 
are not reproducible and very time consuming in analyses. What do you think 
about proposal in our discussion?

Andrei.

 Using Standard JAX-RS API in Syncope (Replace Spring Webservice Stack with 
 Apache CXF)
 --

 Key: SYNCOPE-231
 URL: https://issues.apache.org/jira/browse/SYNCOPE-231
 Project: Syncope
  Issue Type: Improvement
  Components: console, core
Reporter: Jan Bernhardt
Assignee: Jan Bernhardt
 Fix For: 1.2.0

 Attachments: TaskService.patch


 Current REST Interfaces are based on Spring Webservice framework. 
 Goal of this task is to replace Spring with CXF and to relay on JAX-B and 
 JAX-RS annotations rather then Spring annotations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Reopened] (SYNCOPE-293) Modify version layout

2013-01-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò reopened SYNCOPE-293:



I've fixed some issues in the source code that I will commit shortly.

Moreover, there are still visualization issues with Chrome - Firefox looks good 
(see attached screenshot).

 Modify version layout
 -

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, wp.png


 Current layout has a static labels to core and console version.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SYNCOPE-293) Modify version layout

2013-01-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-293:
---

Attachment: welcomeOnChrome.png
infoModalOnFirefox.png
infoModalOnChrome.png

infoModalOnChrome - no CSS (white background, blue link)

infoModalOnFirefox - linked text seems to have different baseline than plain 
text

welcomeOnChrome - bad vertical alignment

 Modify version layout
 -

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Current layout has a static labels to core and console version.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SYNCOPE-296) Modify CSS search botton

2013-01-29 Thread Massimiliano Perrone (JIRA) 
Massimiliano Perrone created SYNCOPE-296:


 Summary: Modify CSS search botton
 Key: SYNCOPE-296
 URL: https://issues.apache.org/jira/browse/SYNCOPE-296
 Project: Syncope
  Issue Type: Bug
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0


Maybe after my css modification, search botton moves on the center of search 
tab.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SYNCOPE-296) Modify CSS search botton

2013-01-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-296:
---

Priority: Trivial  (was: Major)

 Modify CSS search botton
 

 Key: SYNCOPE-296
 URL: https://issues.apache.org/jira/browse/SYNCOPE-296
 Project: Syncope
  Issue Type: Bug
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
Priority: Trivial
 Fix For: 1.1.0


 Maybe after my css modification, search botton moves on the center of search 
 tab.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-296) Modify CSS search botton

2013-01-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565231#comment-13565231
 ] 

Francesco Chicchiriccò commented on SYNCOPE-296:


What do you mean exactly? Currently, the search button in on the center of the 
page: do you want to move it to the center of the search form?
If you are doing so, please check every place where such form is used, not only 
for Users.

 Modify CSS search botton
 

 Key: SYNCOPE-296
 URL: https://issues.apache.org/jira/browse/SYNCOPE-296
 Project: Syncope
  Issue Type: Bug
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
Priority: Trivial
 Fix For: 1.1.0


 Maybe after my css modification, search botton moves on the center of search 
 tab.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-296) Align search botton

2013-01-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565252#comment-13565252
 ] 

Francesco Chicchiriccò commented on SYNCOPE-296:


Ok, so you are moving the search button to left edge, not to the center as you 
are saying the issue description.
Personally, it looks fine.
Please, change the issue description if you are going to commit this.

 Align search botton
 ---

 Key: SYNCOPE-296
 URL: https://issues.apache.org/jira/browse/SYNCOPE-296
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
Priority: Trivial
 Fix For: 1.1.0

 Attachments: after.png, before.png


 Maybe after my css modification, search botton moves on the center of search 
 tab.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SYNCOPE-293) Show information (version, license, ...)

2013-01-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-293:
---

Summary: Show information (version, license, ...)  (was: Modify version 
layout)

 Show information (version, license, ...)
 

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Current layout has a static labels to core and console version.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-293) Modify version layout

2013-01-29 Thread Massimiliano Perrone (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565254#comment-13565254
 ] 

Massimiliano Perrone commented on SYNCOPE-293:
--

[~ilgrosso] I have tested it on Chrome 24 / Opera / Chromium and I have no 
problem :/

 Modify version layout
 -

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Current layout has a static labels to core and console version.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SYNCOPE-296) Align search botton

2013-01-29 Thread Massimiliano Perrone (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Massimiliano Perrone updated SYNCOPE-296:
-

Description: Modify search button position: move it on the left.  (was: 
Maybe after my css modification, search botton moves on the center of search 
tab.)

 Align search botton
 ---

 Key: SYNCOPE-296
 URL: https://issues.apache.org/jira/browse/SYNCOPE-296
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
Priority: Trivial
 Fix For: 1.1.0

 Attachments: after.png, before.png


 Modify search button position: move it on the left.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)

2013-01-29 Thread Francesco Chicchiriccò 

On 29/01/2013 11:17, Andrei Shakirin (JIRA) wrote:

However, I have the following concerns:
1. the 1_0_X branch has the same test that's working flawlessly with JDK 1.6 
and 1.7: why? Is this due to the modification made to make tests re-runnable?

The same test works even in trunk under 1.6 and under some other conditions, 
but is it reliable way to write integration tests? Basically it SHOULDN'T work 
anywhere and runs successfully only occasionally, see [1].
Problem is that some tests can be easily broken by change absolutely not 
related with the test itself, like it happens with Task Service implementation 
(see jira attachment).
I already have seen the same effect for Notification object [2].


Fine.


2. does it make sense to change something in the core only to have easier and 
more reliable tests?

I don't see it as only test related problem. If user configures and uses H2 DB, 
is there guarantee that it cannot happens during normal project using as well?


3. I think it will not be so straightforward to make all necessary adjustments 
to content.xml in order to cope with new id generation

Could you elaborate this? Which issues are you expecting? Do you see other ways 
to fix the problem?


Sorry, I am not following this thread enough to be able to see if there 
are other ways to fix; anyway, you (and Fabio) believe so, and for me 
it's fine, then.


What I mean above is that I am expecting it will take some time to 
adjust the content.xml with ids generated differently: nothing serious, 
only time-consuming. But maybe I'm wrong...



[1] 
http://syncope-dev.1063484.n5.nabble.com/Question-Problem-with-test-UsertTestITCase-issueSYNCOPE279-tt5712389.html
[2] 
http://syncope-dev.1063484.n5.nabble.com/Persistence-id-generation-strategy-TABLE-vs-AUTO-td5711813.html


--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)

2013-01-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565256#comment-13565256
 ] 

Francesco Chicchiriccò commented on SYNCOPE-231:



Fine.


Sorry, I am not following this thread enough to be able to see if there 
are other ways to fix; anyway, you (and Fabio) believe so, and for me 
it's fine, then.

What I mean above is that I am expecting it will take some time to 
adjust the content.xml with ids generated differently: nothing serious, 
only time-consuming. But maybe I'm wrong...


-- 
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/



 Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
 --

 Key: SYNCOPE-231
 URL: https://issues.apache.org/jira/browse/SYNCOPE-231
 Project: Syncope
  Issue Type: Improvement
  Components: console, core
Reporter: Jan Bernhardt
Assignee: Jan Bernhardt
 Fix For: 1.1.0

 Attachments: TaskService.patch


 Current REST Interfaces are based on Spring Webservice framework. 
 Goal of this task is to replace Spring with CXF and to relay on JAX-B and 
 JAX-RS annotations rather then Spring annotations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Console Resource User Mapping error

2013-01-29 Thread Francesco Chicchiriccò 

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 - Account Id, Password - Password, and
a User schema 'surname' attribute - SURNAME column in the table.

The Resource now creates ok, however when I edit it and look at the User
mappings, I see that another column name 'GIVENNAME' is appearing as the
external attribute for the User Account Id and Password mappings.

Can someone confirm this?


Do you have such column GIVENNAME in the table configured for your H2 
resource, right?


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.


Regards.

--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

[jira] [Commented] (SYNCOPE-293) Show information (version, license, ...)

2013-01-29 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565258#comment-13565258
 ] 

Hudson commented on SYNCOPE-293:


Integrated in Syncope-trunk #23 (See 
[https://builds.apache.org/job/Syncope-trunk/23/])
[SYNCOPE-293] Removing unwanted pom properties + fixing positioning issues 
under Firefox (Revision 1439799)

 Result = SUCCESS
ilgrosso : 
Files : 
* /syncope/trunk/console/pom.xml
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeApplication.java
* /syncope/trunk/console/src/main/resources/applicationContext.xml
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/BasePage.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/WelcomePage.html
* /syncope/trunk/console/src/main/webapp/img/info.png
* /syncope/trunk/pom.xml


 Show information (version, license, ...)
 

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Currently there is only a static label with core and console versions.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-293) Show information (version, license, ...)

2013-01-29 Thread fabio martelli (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565260#comment-13565260
 ] 

fabio martelli commented on SYNCOPE-293:


I confirm the bug on Chrome.
Safari is good.

 Show information (version, license, ...)
 

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Currently there is only a static label with core and console versions.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Console Resource User Mapping error

2013-01-29 Thread Colm O hEigeartaigh 
 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 problem is that it is doing this for the AccountId + Password rows?

Colm.


On Tue, Jan 29, 2013 at 10:35 AM, Francesco Chicchiriccò 
ilgro...@apache.org wrote:

 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 - Account Id, Password - Password, and
 a User schema 'surname' attribute - SURNAME column in the table.

 The Resource now creates ok, however when I edit it and look at the User
 mappings, I see that another column name 'GIVENNAME' is appearing as the
 external attribute for the User Account Id and Password mappings.

 Can someone confirm this?


 Do you have such column GIVENNAME in the table configured for your H2
 resource, right?

 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.


 Regards.

 --
 Francesco Chicchiriccò

 ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
 http://people.apache.org/~**ilgrosso/http://people.apache.org/~ilgrosso/

[jira] [Commented] (SYNCOPE-293) Show information (version, license, ...)

2013-01-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565273#comment-13565273
 ] 

Francesco Chicchiriccò commented on SYNCOPE-293:


Please also try to login with other user than admin (for example user1 / 
password) since plain users, differently from admin, have a link to edit their 
own profile: the result is quite ugly ATM.

 Show information (version, license, ...)
 

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Currently there is only a static label with core and console versions.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings

2013-01-29 Thread Colm O hEigeartaigh (JIRA) 
Colm O hEigeartaigh created SYNCOPE-297:
---

 Summary: External Attributes are showing up for AccoundId/Password 
in Resource User Mappings
 Key: SYNCOPE-297
 URL: https://issues.apache.org/jira/browse/SYNCOPE-297
 Project: Syncope
  Issue Type: Bug
Reporter: Colm O hEigeartaigh
 Fix For: 1.1.0



I have a Database Connector for a H2 backend with a simple table. I am creating 
a Resource User Mapping of Username - Account Id, Password - Password, and a 
User schema 'surname' attribute - SURNAME column in the table.

The Resource now creates ok, however when I edit it and look at the User 
mappings, I see that another column name 'GIVENNAME' is appearing as the 
external attribute for the User Account Id and Password mappings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: svn commit: r1439829 - in /syncope/branches/1_0_X: ./ console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java

2013-01-29 Thread Colm O hEigeartaigh 
Hi Fabio,

You're right - I'll fix it.

Colm.

On Tue, Jan 29, 2013 at 10:58 AM, Fabio Martelli
fabio.marte...@gmail.comwrote:


 Il giorno 29/gen/2013, alle ore 11.55, cohei...@apache.org ha scritto:

  Author: coheigea
  Date: Tue Jan 29 10:55:14 2013
  New Revision: 1439829
 
  URL: http://svn.apache.org/viewvc?rev=1439829view=rev
  Log:
  Log Resource management exception properly
 
  Modified:
 syncope/branches/1_0_X/   (props changed)
 
  
 syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java
 
  Propchange: syncope/branches/1_0_X/
 
 --
   Merged /syncope/trunk:r1439825
 
  Modified:
 syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java
  URL:
 http://svn.apache.org/viewvc/syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java?rev=1439829r1=1439828r2=1439829view=diff
 
 ==
  ---
 syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java
 (original)
  +++
 syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java
 Tue Jan 29 10:55:14 2013
  @@ -111,7 +111,8 @@ public class ResourceModalPage extends B
  window.close(target);
 
  } catch (Exception e) {
  -LOG.error(Failuer managing resource {},
 resourceTO);
  +LOG.error(Failure managing resource {},
 resourceTO);
  +LOG.error(Resource Management Exception:, e);

 Hi Colm, why this modification?
 Why not the just the following

 LOG.error(Failuer managing resource {}, resourceTO, e);

 Best regards,
 F.

  error(new ResourceModel(error,
 error).getObject() + : + e.getMessage());
  target.add(feedbackPanel);
  }
  @@ -162,4 +163,4 @@ public class ResourceModalPage extends B
  return target;
  }
  }
  -}
  \ No newline at end of file
  +}
 
 




-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: svn commit: r1439829 - in /syncope/branches/1_0_X: ./ console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java

2013-01-29 Thread Francesco Chicchiriccò 

On 29/01/2013 12:02, Colm O hEigeartaigh wrote:

Hi Fabio,

You're right - I'll fix it.


Does it mean you are going to replace failure with failuer as well? ;-)

--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

[jira] [Resolved] (SYNCOPE-296) Align search botton

2013-01-29 Thread Massimiliano Perrone (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Massimiliano Perrone resolved SYNCOPE-296.
--

Resolution: Fixed

http://svn.apache.org/viewvc?rev=1439836view=rev

 Align search botton
 ---

 Key: SYNCOPE-296
 URL: https://issues.apache.org/jira/browse/SYNCOPE-296
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
Priority: Trivial
 Fix For: 1.1.0

 Attachments: after.png, before.png


 Modify search button position: move it on the left.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-296) Align search botton

2013-01-29 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565295#comment-13565295
 ] 

Hudson commented on SYNCOPE-296:


Integrated in Syncope-trunk #24 (See 
[https://builds.apache.org/job/Syncope-trunk/24/])
Fixed SYNCOPE-296 (Revision 1439836)

 Result = SUCCESS
massi : 
Files : 
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Roles.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/UserOwnerSelectModalPage.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Users.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/WelcomePage.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/RoleTabPanel.html
* /syncope/trunk/console/src/main/webapp/css/fieldstyle.css


 Align search botton
 ---

 Key: SYNCOPE-296
 URL: https://issues.apache.org/jira/browse/SYNCOPE-296
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
Priority: Trivial
 Fix For: 1.1.0

 Attachments: after.png, before.png


 Modify search button position: move it on the left.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Issue with serializing ReportTO as it has an interface ReportletConf

2013-01-29 Thread Christian Schneider 
I have an issue serializing and unserializing ReportTO using jaxb.

The problem is at the ReportletConf list:
public ListReportletConf getReportletConfs() {
return reportletConfs;
}

As ReportletConf is an interface JAXB can not handle it. So we get an
IllegalAnnotationException or similar and JAXB does not even initialize.

So I introduced the annotation below. This allowed the serialization to run.
@XmlElement(type=AbstractReportletConf.class)

The problem now is that the result of the serialization is not complete
and can not be deserialized into the actual classes.
This is how it looks (in an example I did with simplified classes:
?xml version=1.0 encoding=UTF-8
standalone=yes?reportreportletConfsnametest/namedescriptiondesc/description/reportletConfs/report

As you can see there is not enough information to detect the real class.

So I tried to change the signature to use the abstract class and not use
the annotation:
public ListAbstractReportletConf getReportletConfs()

This works:
?xml version=1.0 encoding=UTF-8
standalone=yes?reportreportletConfs
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=staticReportletConfnametest/namedescriptiondesc/description/reportletConfs/report

From the xsi:type jaxb knows the class to instantiate.

So there are the following questions:

- Is there a better way to achieve correct serialization of interfaces ?
- Would it be ok if I change ReportletTO to use the abstract class?
- I would like to avoid the xsi:type and instead have elements for each
class extending AbstractReportletConf. Is that possible?

Best regards

Christian

-- 
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

Re: Issue with serializing ReportTO as it has an interface ReportletConf

2013-01-29 Thread Francesco Chicchiriccò 

On 29/01/2013 13:09, Christian Schneider wrote:

I have an issue serializing and unserializing ReportTO using jaxb.

The problem is at the ReportletConf list:
 public ListReportletConf getReportletConfs() {
 return reportletConfs;
 }

As ReportletConf is an interface JAXB can not handle it. So we get an
IllegalAnnotationException or similar and JAXB does not even initialize.

So I introduced the annotation below. This allowed the serialization to run.
 @XmlElement(type=AbstractReportletConf.class)

The problem now is that the result of the serialization is not complete
and can not be deserialized into the actual classes.
This is how it looks (in an example I did with simplified classes:
?xml version=1.0 encoding=UTF-8
standalone=yes?reportreportletConfsnametest/namedescriptiondesc/description/reportletConfs/report

As you can see there is not enough information to detect the real class.

So I tried to change the signature to use the abstract class and not use
the annotation:
public ListAbstractReportletConf getReportletConfs()

This works:
?xml version=1.0 encoding=UTF-8
standalone=yes?reportreportletConfs
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:type=staticReportletConfnametest/namedescriptiondesc/description/reportletConfs/report

 From the xsi:type jaxb knows the class to instantiate.

So there are the following questions:

- Is there a better way to achieve correct serialization of interfaces ?


I am not an expert at all of JAXB, passing this question.


- Would it be ok if I change ReportletTO to use the abstract class?


Not good, but still acceptable IMHO.


- I would like to avoid the xsi:type and instead have elements for each
class extending AbstractReportletConf. Is that possible?


Same as above; we will have to remember this when we will finally write 
a wiki page about how to create custom reports via reportlets.


Regards.

--
Francesco Chicchiriccò

ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/

[jira] [Commented] (SYNCOPE-293) Show information (version, license, ...)

2013-01-29 Thread Massimiliano Perrone (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565321#comment-13565321
 ] 

Massimiliano Perrone commented on SYNCOPE-293:
--

Why two steps to edit user profile?
Why not directly link username label to editModalPage?

 Show information (version, license, ...)
 

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Currently there is only a static label with core and console versions.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-293) Show information (version, license, ...)

2013-01-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565322#comment-13565322
 ] 

Francesco Chicchiriccò commented on SYNCOPE-293:


If you find this (i.e. link editModalPage to username) easier, go with it.

 Show information (version, license, ...)
 

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Currently there is only a static label with core and console versions.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SYNCOPE-298) Persistence beans: change AUTO Id generation strategy to TABLE

2013-01-29 Thread Andrei Shakirin (JIRA) 
Andrei Shakirin created SYNCOPE-298:
---

 Summary: Persistence beans: change AUTO Id generation strategy to 
TABLE
 Key: SYNCOPE-298
 URL: https://issues.apache.org/jira/browse/SYNCOPE-298
 Project: Syncope
  Issue Type: Improvement
  Components: core
Reporter: Andrei Shakirin
 Fix For: 1.2.0


Currently AUTO Id generation strategy works unstable under high 
load/concurrency conditions at least for H2 DB. [1], [2]

Possible solution of this problem is migration AUTO to TABLE Id generation 
strategy for all persistence domain objects.

[1] 
http://syncope-dev.1063484.n5.nabble.com/Question-Problem-with-test-UsertTestITCase-issueSYNCOPE279-tt5712389.html
[2] 
http://syncope-dev.1063484.n5.nabble.com/Persistence-id-generation-strategy-TABLE-vs-AUTO-td5711813.html


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-122) Password change on an external resource only

2013-01-29 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565345#comment-13565345
 ] 

Hudson commented on SYNCOPE-122:


Integrated in Syncope-trunk #25 (See 
[https://builds.apache.org/job/Syncope-trunk/25/])
[SYNCOPE-122] Fixing attempting re-enablement of enabled user (Revision 
1439860)
[SYNCOPE-122] Extension on console almost done: only missing on-the-fly 
selection for resources added (directly or via role selection) but not yet 
submitted (Revision 1439854)

 Result = SUCCESS
ilgrosso : 
Files : 
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusUtils.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRestClient.java

ilgrosso : 
Files : 
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusBean.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusUtils.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConnectorModalPage.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/EditUserModalPage.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/UserModalPage.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/AbstractSearchResultPanel.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/StatusPanel.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/UserSearchResultPanel.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRestClient.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/ActionLink.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/ActionLinksPanel.java
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/ResultStatusModalPage.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/UserModalPage.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/UserModalPage.properties
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/UserModalPage_it.properties
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/StatusPanel.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/form/ActionLinksPanel.html
* /syncope/trunk/console/src/main/webapp/img/actions/enable.png
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/ConfigurationTestITCase.java
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/ConnInstanceTestITCase.java
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/ReportTestITCase.java
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/ResourceTestITCase.java
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/RoleTestITCase.java
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/SchemaTestITCase.java
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/TaskTestITCase.java
* 
/syncope/trunk/console/src/test/java/org/apache/syncope/console/UserTestITCase.java


 Password change on an external resource only
 

 Key: SYNCOPE-122
 URL: https://issues.apache.org/jira/browse/SYNCOPE-122
 Project: Syncope
  Issue Type: New Feature
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 1.1.0


 Give option to change password only on one or more connected external 
 resources; currently it's only possible to change password on Syncope core 
 and then propagate accordingly to the connected external resources.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-298) Persistence beans: change AUTO Id generation strategy to TABLE

2013-01-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565388#comment-13565388
 ] 

Francesco Chicchiriccò commented on SYNCOPE-298:


Andrei, confirmed that the build works again with JDK 1.7, please ignore my 
comment.

 Persistence beans: change AUTO Id generation strategy to TABLE
 --

 Key: SYNCOPE-298
 URL: https://issues.apache.org/jira/browse/SYNCOPE-298
 Project: Syncope
  Issue Type: Improvement
  Components: core
Reporter: Andrei Shakirin
 Fix For: 1.2.0


 Currently AUTO Id generation strategy works unstable under high 
 load/concurrency conditions at least for H2 DB. [1], [2]
 Possible solution of this problem is migration AUTO to TABLE Id generation 
 strategy for all persistence domain objects.
 [1] 
 http://syncope-dev.1063484.n5.nabble.com/Question-Problem-with-test-UsertTestITCase-issueSYNCOPE279-tt5712389.html
 [2] 
 http://syncope-dev.1063484.n5.nabble.com/Persistence-id-generation-strategy-TABLE-vs-AUTO-td5711813.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SYNCOPE-293) Show information (version, license, ...)

2013-01-29 Thread Massimiliano Perrone (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Massimiliano Perrone resolved SYNCOPE-293.
--

Resolution: Fixed

Conclusive commit: http://svn.apache.org/viewvc?rev=1439917view=rev

 Show information (version, license, ...)
 

 Key: SYNCOPE-293
 URL: https://issues.apache.org/jira/browse/SYNCOPE-293
 Project: Syncope
  Issue Type: Improvement
  Components: console
Reporter: Massimiliano Perrone
Assignee: Massimiliano Perrone
 Fix For: 1.1.0

 Attachments: bp.png, infoModalOnChrome.png, infoModalOnFirefox.png, 
 welcomeOnChrome.png, wp.png


 Currently there is only a static label with core and console versions.
 Add a new Link to open a ModalPage with version and other project information 
 (eg. link to license)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)

2013-01-29 Thread Andrei Shakirin (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565426#comment-13565426
 ] 

Andrei Shakirin commented on SYNCOPE-231:
-

I am merging it now. 
Unfortunately one more test in UserTestITCase doesn't run now, because of the 
same AbstractVirAttribute AUTO Id generation strategy problem :(

Andrei.

 Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)
 --

 Key: SYNCOPE-231
 URL: https://issues.apache.org/jira/browse/SYNCOPE-231
 Project: Syncope
  Issue Type: Improvement
  Components: console, core
Reporter: Jan Bernhardt
Assignee: Jan Bernhardt
 Fix For: 1.1.0

 Attachments: TaskService.patch


 Current REST Interfaces are based on Spring Webservice framework. 
 Goal of this task is to replace Spring with CXF and to relay on JAX-B and 
 JAX-RS annotations rather then Spring annotations.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-291) Move NotFoundException to core.persistence.dao

2013-01-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565437#comment-13565437
 ] 

Francesco Chicchiriccò commented on SYNCOPE-291:


Is this issue still unfinished?

 Move NotFoundException to core.persistence.dao
 --

 Key: SYNCOPE-291
 URL: https://issues.apache.org/jira/browse/SYNCOPE-291
 Project: Syncope
  Issue Type: Improvement
  Components: core
Affects Versions: 1.1.0
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 1.1.0


 The NotFoundException is currently located in util which is not such a
 good place as it is part of the dao as well as service interfaces. 
 Like discussed on the dev list we agree to move this exception to 
 core.persistence.dao.
 For the rest services the exception will be mapped to the 
 rs.NotFoundException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (SYNCOPE-291) Move NotFoundException to core.persistence.dao

2013-01-29 Thread Christian Schneider (JIRA) 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider resolved SYNCOPE-291.
-

Resolution: Fixed

Oh sorry .. it is done

 Move NotFoundException to core.persistence.dao
 --

 Key: SYNCOPE-291
 URL: https://issues.apache.org/jira/browse/SYNCOPE-291
 Project: Syncope
  Issue Type: Improvement
  Components: core
Affects Versions: 1.1.0
Reporter: Christian Schneider
Assignee: Christian Schneider
 Fix For: 1.1.0


 The NotFoundException is currently located in util which is not such a
 good place as it is part of the dao as well as service interfaces. 
 Like discussed on the dev list we agree to move this exception to 
 core.persistence.dao.
 For the rest services the exception will be mapped to the 
 rs.NotFoundException.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-128) Self-registration

2013-01-29 Thread Denis Signoretto (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565474#comment-13565474
 ] 

Denis Signoretto commented on SYNCOPE-128:
--

I have created an initial version of the self registration page [1] on the wiki.

I can still improve Opt-in description:

1) Customization of token: lenght and expriration time
2) How token validation occurs

[1] - https://cwiki.apache.org/confluence/display/SYNCOPE/Self+registration

 Self-registration
 -

 Key: SYNCOPE-128
 URL: https://issues.apache.org/jira/browse/SYNCOPE-128
 Project: Syncope
  Issue Type: Task
  Components: documentation
Reporter: Francesco Chicchiriccò
Assignee: Denis Signoretto
 Fix For: 1.1.0


 Document how it works, how it can be configured and tweaked.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings

2013-01-29 Thread Jan Bernhardt (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565484#comment-13565484
 ] 

Jan Bernhardt commented on SYNCOPE-297:
---

Problem could be related to Internal Server Error in 
ConnInstanceController.getSchemaNames(...) Line 334 ?

I get strange exception behavior here, when using H2 connector...

 External Attributes are showing up for AccoundId/Password in Resource User 
 Mappings
 ---

 Key: SYNCOPE-297
 URL: https://issues.apache.org/jira/browse/SYNCOPE-297
 Project: Syncope
  Issue Type: Bug
Reporter: Colm O hEigeartaigh
 Fix For: 1.1.0

 Attachments: Screenshot.png


 I have a Database Connector for a H2 backend with a simple table. I am 
 creating a Resource User Mapping of Username - Account Id, Password - 
 Password, and a User schema 'surname' attribute - SURNAME column in the 
 table.
 The Resource now creates ok, however when I edit it and look at the User 
 mappings, I see that another column name 'GIVENNAME' is appearing as the 
 external attribute for the User Account Id and Password mappings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (SYNCOPE-299) Add row to display selector in resources

2013-01-29 Thread Denis Signoretto (JIRA) 
Denis Signoretto created SYNCOPE-299:


 Summary: Add row to display selector in resources
 Key: SYNCOPE-299
 URL: https://issues.apache.org/jira/browse/SYNCOPE-299
 Project: Syncope
  Issue Type: Improvement
  Components: console
Affects Versions: 1.0.5
Reporter: Denis Signoretto


Allow resources list to display more than 10 resources per page (add the Rows 
to display pager)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SYNCOPE-299) Add row to display selector in resources

2013-01-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-299:
---

Fix Version/s: 1.1.0
   1.0.6

 Add row to display selector in resources
 --

 Key: SYNCOPE-299
 URL: https://issues.apache.org/jira/browse/SYNCOPE-299
 Project: Syncope
  Issue Type: Improvement
  Components: console
Affects Versions: 1.0.5
Reporter: Denis Signoretto
Priority: Minor
 Fix For: 1.0.6, 1.1.0


 Allow resources list to display more than 10 resources per page (add the 
 Rows to display pager)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (SYNCOPE-299) Add row to display selector in resources

2013-01-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Francesco Chicchiriccò updated SYNCOPE-299:
---

Priority: Minor  (was: Major)

 Add row to display selector in resources
 --

 Key: SYNCOPE-299
 URL: https://issues.apache.org/jira/browse/SYNCOPE-299
 Project: Syncope
  Issue Type: Improvement
  Components: console
Affects Versions: 1.0.5
Reporter: Denis Signoretto
Priority: Minor

 Allow resources list to display more than 10 resources per page (add the 
 Rows to display pager)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (SYNCOPE-298) Persistence beans: change AUTO Id generation strategy to TABLE

2013-01-29 Thread Hudson (JIRA) 

[ 
https://issues.apache.org/jira/browse/SYNCOPE-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565575#comment-13565575
 ] 

Hudson commented on SYNCOPE-298:


Integrated in Syncope-trunk #29 (See 
[https://builds.apache.org/job/Syncope-trunk/29/])
[SYNCOPE-231] Applied TaskService patch. UserTestITCase contains workaround 
for SYNCOPE-298 (Revision 1439945)

 Result = SUCCESS
ashakirin : 
Files : 
* 
/syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/TaskServiceProxy.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/TaskService.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/TaskRestClient.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/services/TaskServiceImpl.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/TaskTestITCaseJAXRS.java


 Persistence beans: change AUTO Id generation strategy to TABLE
 --

 Key: SYNCOPE-298
 URL: https://issues.apache.org/jira/browse/SYNCOPE-298
 Project: Syncope
  Issue Type: Improvement
  Components: core
Reporter: Andrei Shakirin
 Fix For: 1.2.0


 Currently AUTO Id generation strategy works unstable under high 
 load/concurrency conditions at least for H2 DB. [1], [2]
 Possible solution of this problem is migration AUTO to TABLE Id generation 
 strategy for all persistence domain objects.
 [1] 
 http://syncope-dev.1063484.n5.nabble.com/Question-Problem-with-test-UsertTestITCase-issueSYNCOPE279-tt5712389.html
 [2] 
 http://syncope-dev.1063484.n5.nabble.com/Persistence-id-generation-strategy-TABLE-vs-AUTO-td5711813.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira