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

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #38 (See 
[https://builds.apache.org/job/Syncope-trunk/38/])
SYNCOPE-231 Deleting test again as the is already EntitlementTest which is 
extends AuthenticationTest (Revision 1440874)

 Result = SUCCESS
cschneider : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/AuthenticationTestITCaseJAXRS.java


> 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

[DISCUSS] SchemaType and SchemaService

[Jan Bernhardt]

Hi Syncoper,

We know three different schema types in syncope "normal Schema", "derived 
Schema" and "virtual Schema". In Spring REST Interface these schemas are mapped 
to three different controllers which are basically doing the same thing, just 
for each type.

Therefore I only created a single SchemaService for new CXF REST Service, 
capable of handling all three kinds. To distinguish with type of Schema should 
be handled (e.g. returned for a list operation) I created a new enum SchemaType.

The topic to discuss however is, that in org.apache.syncope.common.types there 
is already a class named SchemaType containing data types for (user, role, 
membership) schema values (e.g. String, Long, Date, ...). My proposal would be 
to rename existing SchemaType class to EntitySchemaType (similar to 
EntityViolationType) and move SchemaType currently included in SchemaService 
Interface to org.apache.syncope.common.types.SchemaType.

Any objections?

Best regards.
Jan

Re: [DISCUSS] SchemaType and SchemaService

[Fabio Martelli]

Il giorno 31/gen/2013, alle ore 09.58, Jan Bernhardt ha scritto:

> Hi Syncoper,
> 
> We know three different schema types in syncope "normal Schema", "derived 
> Schema" and "virtual Schema". In Spring REST Interface these schemas are 
> mapped to three different controllers which are basically doing the same 
> thing, just for each type.
> 
> Therefore I only created a single SchemaService for new CXF REST Service, 
> capable of handling all three kinds. To distinguish with type of Schema 
> should be handled (e.g. returned for a list operation) I created a new enum 
> SchemaType.
> 
> The topic to discuss however is, that in org.apache.syncope.common.types 
> there is already a class named SchemaType containing data types for (user, 
> role, membership) schema values (e.g. String, Long, Date, ...). My proposal 
> would be to rename existing SchemaType class to EntitySchemaType (similar to 
> EntityViolationType) and move SchemaType currently included in SchemaService 
> Interface to org.apache.syncope.common.types.SchemaType.
+1
no objections
> 
> Any objections?
> 
> Best regards.
> Jan
> 

Re: [DISCUSS] SchemaType and SchemaService

[Jean-Baptiste Onofré]

+1, it sounds good to me.

Regards
JB

On 01/31/2013 09:58 AM, Jan Bernhardt wrote:

Hi Syncoper,

We know three different schema types in syncope "normal Schema", "derived Schema" and 
"virtual Schema". In Spring REST Interface these schemas are mapped to three different controllers 
which are basically doing the same thing, just for each type.

Therefore I only created a single SchemaService for new CXF REST Service, 
capable of handling all three kinds. To distinguish with type of Schema should 
be handled (e.g. returned for a list operation) I created a new enum SchemaType.

The topic to discuss however is, that in org.apache.syncope.common.types there 
is already a class named SchemaType containing data types for (user, role, 
membership) schema values (e.g. String, Long, Date, ...). My proposal would be 
to rename existing SchemaType class to EntitySchemaType (similar to 
EntityViolationType) and move SchemaType currently included in SchemaService 
Interface to org.apache.syncope.common.types.SchemaType.

Any objections?

Best regards.
Jan




--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

RE: [DISCUSS] SchemaType and SchemaService

[Andrei Shakirin]

Hi,

Related topic: I going to use AttributableType in WorkflowService instead 
strings "user" and "role".
Any objections?

Regards,
Andrei.

> -Original Message-
> From: Jan Bernhardt [mailto:jbernha...@talend.com]
> Sent: Donnerstag, 31. Januar 2013 09:58
> To: dev@syncope.apache.org
> Subject: [DISCUSS] SchemaType and SchemaService
> 
> Hi Syncoper,
> 
> We know three different schema types in syncope "normal Schema",
> "derived Schema" and "virtual Schema". In Spring REST Interface these
> schemas are mapped to three different controllers which are basically doing
> the same thing, just for each type.
> 
> Therefore I only created a single SchemaService for new CXF REST Service,
> capable of handling all three kinds. To distinguish with type of Schema should
> be handled (e.g. returned for a list operation) I created a new enum
> SchemaType.
> 
> The topic to discuss however is, that in org.apache.syncope.common.types
> there is already a class named SchemaType containing data types for (user,
> role, membership) schema values (e.g. String, Long, Date, ...). My proposal
> would be to rename existing SchemaType class to EntitySchemaType (similar
> to EntityViolationType) and move SchemaType currently included in
> SchemaService Interface to
> org.apache.syncope.common.types.SchemaType.
> 
> Any objections?
> 
> Best regards.
> Jan

[jira] [Created] (SYNCOPE-302) Error when accessing the Resources page as non-admin

[JIRA]

Francesco Chicchiriccò created SYNCOPE-302:
--

 Summary: Error when accessing the Resources page as non-admin
 Key: SYNCOPE-302
 URL: https://issues.apache.org/jira/browse/SYNCOPE-302
 Project: Syncope
  Issue Type: Bug
  Components: console
Affects Versions: 1.1.0
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 1.1.0


When accessing the Resources page as plain user, a Stacktrace (403 Forbidden) 
is thrown.

--
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-302) Error when accessing the Resources page as non-admin

[JIRA]

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

Francesco Chicchiriccò resolved SYNCOPE-302.


Resolution: Fixed

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

> Error when accessing the Resources page as non-admin
> 
>
> Key: SYNCOPE-302
> URL: https://issues.apache.org/jira/browse/SYNCOPE-302
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 1.1.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
>
> When accessing the Resources page as plain user, a Stacktrace (403 Forbidden) 
> is thrown.

--
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: [DISCUSS] SchemaType and SchemaService

[Francesco Chicchiriccò]

On 31/01/2013 09:58, Jan Bernhardt wrote:

Hi Syncoper,

We know three different schema types in syncope "normal Schema", "derived Schema" and 
"virtual Schema". In Spring REST Interface these schemas are mapped to three different controllers 
which are basically doing the same thing, just for each type.

Therefore I only created a single SchemaService for new CXF REST Service, 
capable of handling all three kinds. To distinguish with type of Schema should 
be handled (e.g. returned for a list operation) I created a new enum SchemaType.

The topic to discuss however is, that in org.apache.syncope.common.types there 
is already a class named SchemaType containing data types for (user, role, 
membership) schema values (e.g. String, Long, Date, ...). My proposal would be 
to rename existing SchemaType class to EntitySchemaType (similar to 
EntityViolationType) and move SchemaType currently included in SchemaService 
Interface to org.apache.syncope.common.types.SchemaType.

Any objections?


Not in general; only, I would rather rename the existing SchemaType to 
AttributeSchemaType (or AttrSchemaType) since Entity* is usually 
referring to JPA entities.


Regards.

--
Francesco Chicchiriccò

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

Re: [DISCUSS] SchemaType and SchemaService

[Francesco Chicchiriccò]

On 31/01/2013 11:30, Andrei Shakirin wrote:

Hi,

Related topic: I going to use AttributableType in WorkflowService instead strings "user" 
and "role".
Any objections?


None if you take care in the code that AttirbutableType can also be 
MEMBERSHIP in general while in the workflow context this is naturally 
meaningless.


Regards.

--
Francesco Chicchiriccò

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

RE: [DISCUSS] SchemaType and SchemaService

[Andrei Shakirin]

> None if you take care in the code that AttirbutableType can also be
> MEMBERSHIP in general while in the workflow context this is naturally
> meaningless.

Sure, it will BadRequest in case of MEMBERSHIP.

Andrei.

> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Donnerstag, 31. Januar 2013 11:48
> To: dev@syncope.apache.org
> Subject: Re: [DISCUSS] SchemaType and SchemaService
> 
> On 31/01/2013 11:30, Andrei Shakirin wrote:
> > Hi,
> >
> > Related topic: I going to use AttributableType in WorkflowService instead
> strings "user" and "role".
> > Any objections?
> 
> None if you take care in the code that AttirbutableType can also be
> MEMBERSHIP in general while in the workflow context this is naturally
> meaningless.
> 
> Regards.
> 
> --
> 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)

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #39 (See 
[https://builds.apache.org/job/Syncope-trunk/39/])
[SYNCOPE-231]
* adding JAVA DOC for Service Interfaces
* Fixing getOptions Bug in UserRequestService (implementations)
* Code cleanup (Revision 1440895)
SYNCOPE-231 Do not read UserRequest after create as it will fail with anon user 
(Revision 1440889)
SYNCOPE-231 Make AuthenticationTest rerunable (Revision 1440888)

 Result = SUCCESS
jbernhardt : 
Files : 
* 
/syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/UserRequestServiceProxy.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ReportService.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ResourceService.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/RoleService.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserRequestServiceImpl.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java

cschneider : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java

cschneider : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java


> 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-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #40 (See 
[https://builds.apache.org/job/Syncope-trunk/40/])
[SYNCOPE-231] Added WorkflowServiceImpl and Test (Revision 1440904)
[SYNCOPE-231]
* adding missing JAX-RS Tests (Revision 1440902)

 Result = FAILURE
ashakirin : 
Files : 
* 
/syncope/trunk/build-tools/src/main/resources/org/apache/syncope/checkstyle.xml
* 
/syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/util/CollectionWrapper.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/NotificationRestClient.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/WorkflowRestClient.java
* /syncope/trunk/core/src/main/resources/restContext.xml
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java

jbernhardt : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/DerivedSchemaTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/SearchTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/TaskTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/UserTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/VirtualSchemaTestITCaseJAXRS.java


> 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-302) Error when accessing the Resources page as non-admin

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567563#comment-13567563
 ] 

Hudson commented on SYNCOPE-302:


Integrated in Syncope-trunk #40 (See 
[https://builds.apache.org/job/Syncope-trunk/40/])
[SYNCOPE-302] Fix (Revision 1440901)

 Result = FAILURE
ilgrosso : 
Files : 
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ConnObjectTO.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ResourceTO.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientCompositeErrorException.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Resources.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/ResourceDataBinder.java


> Error when accessing the Resources page as non-admin
> 
>
> Key: SYNCOPE-302
> URL: https://issues.apache.org/jira/browse/SYNCOPE-302
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 1.1.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
>
> When accessing the Resources page as plain user, a Stacktrace (403 Forbidden) 
> is thrown.

--
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

Syncope-trunk - Build # 40 - Failure

[Apache Jenkins Server]

The Apache Jenkins build system has built Syncope-trunk (build #40)

Status: Failure

Check console output at https://builds.apache.org/job/Syncope-trunk/40/ to view 
the results.

Syncope-trunk - Build # 41 - Aborted

[Apache Jenkins Server]

The Apache Jenkins build system has built Syncope-trunk (build #41)

Status: Aborted

Check console output at https://builds.apache.org/job/Syncope-trunk/41/ to view 
the results.

Syncope-trunk - Build # 42 - Aborted

[Apache Jenkins Server]

The Apache Jenkins build system has built Syncope-trunk (build #42)

Status: Aborted

Check console output at https://builds.apache.org/job/Syncope-trunk/42/ to view 
the results.

Re: svn commit: r1440904 - in /syncope/trunk: build-tools/src/main/resources/org/apache/syncope/ client/src/main/java/org/apache/syncope/client/services/proxy/ common/src/main/java/org/apache/syncope/

[Francesco Chicchiriccò]

Hi Andrei,
as stated by latest failures on Jenkins, it seems that your commit broke 
the build, in particular your modification to 
core/src/main/resources/restContent.xml adds a reference to 
workflowServiceImpl that cannot be resolved by Spring.


Have you forgotten to commit something else or just to run the testsuite 
before committing? ;-)


I have just reverted this change to make the build succeed again (at 
least on JDK 1.6, but this is another story...): if you still need it, 
please take care that everything is still working before committing.


Regards.


On 31/01/2013 11:58, ashaki...@apache.org wrote:

Author: ashakirin
Date: Thu Jan 31 10:58:31 2013
New Revision: 1440904

URL: http://svn.apache.org/viewvc?rev=1440904&view=rev
Log:
[SYNCOPE-231] Added WorkflowServiceImpl and Test

Modified:
 
syncope/trunk/build-tools/src/main/resources/org/apache/syncope/checkstyle.xml
 
syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java
 
syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java
 
syncope/trunk/common/src/main/java/org/apache/syncope/common/util/CollectionWrapper.java
 
syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/NotificationRestClient.java
 
syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/WorkflowRestClient.java
 syncope/trunk/core/src/main/resources/restContext.xml
 
syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java

Modified: 
syncope/trunk/build-tools/src/main/resources/org/apache/syncope/checkstyle.xml
URL: 
http://svn.apache.org/viewvc/syncope/trunk/build-tools/src/main/resources/org/apache/syncope/checkstyle.xml?rev=1440904&r1=1440903&r2=1440904&view=diff
==
--- 
syncope/trunk/build-tools/src/main/resources/org/apache/syncope/checkstyle.xml 
(original)
+++ 
syncope/trunk/build-tools/src/main/resources/org/apache/syncope/checkstyle.xml 
Thu Jan 31 10:58:31 2013
@@ -177,7 +177,7 @@ under the License.
  
  
  
-
+
  
  
  

Modified: 
syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java
URL: 
http://svn.apache.org/viewvc/syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java?rev=1440904&r1=1440903&r2=1440904&view=diff
==
--- 
syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java
 (original)
+++ 
syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java
 Thu Jan 31 10:58:31 2013
@@ -22,6 +22,7 @@ import java.util.Arrays;
  import java.util.List;
  import org.apache.syncope.common.services.WorkflowService;
  import org.apache.syncope.common.to.WorkflowDefinitionTO;
+import org.apache.syncope.common.types.AttributableType;
  import org.springframework.web.client.RestTemplate;
  
  public class WorkflowServiceProxy extends SpringServiceProxy implements WorkflowService {

@@ -31,17 +32,19 @@ public class WorkflowServiceProxy extend
  }
  
  @Override

-public WorkflowDefinitionTO getDefinition(final String type) {
-return getRestTemplate().getForObject(baseUrl + "workflow/definition/" 
+ type, WorkflowDefinitionTO.class);
+public WorkflowDefinitionTO getDefinition(final AttributableType type) {
+return getRestTemplate().getForObject(baseUrl + "workflow/definition/" 
+ type.name().toLowerCase(),
+WorkflowDefinitionTO.class);
  }
  
  @Override

-public void updateDefinition(final String type, final WorkflowDefinitionTO 
definition) {
-getRestTemplate().put(baseUrl + "workflow/definition/" + type, 
definition);
+public void updateDefinition(final AttributableType type, final 
WorkflowDefinitionTO definition) {
+getRestTemplate().put(baseUrl + "workflow/definition/" + 
type.name().toLowerCase(), definition);
  }
  
  @Override

-public List getDefinedTasks(final String type) {
-return Arrays.asList(getRestTemplate().getForObject(baseUrl + 
"workflow/tasks/{type}", String[].class, type));
+public List getDefinedTasks(final AttributableType type) {
+return Arrays.asList(getRestTemplate().getForObject(baseUrl + 
"workflow/tasks/{type}", String[].class,
+type.name().toLowerCase()));
  }
  }

Modified: 
syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java
URL: 
http://svn.apache.org/viewvc/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java?rev=1440904&r1=1440903&r2=1440904&view=diff
==
--- 
syncope/trunk/common/src/main/java/org/apache/syncope/common

RE: svn commit: r1440904 - in /syncope/trunk: build-tools/src/main/resources/org/apache/syncope/ client/src/main/java/org/apache/syncope/client/services/proxy/ common/src/main/java/org/apache/syncope/

[Andrei Shakirin]

Hi Francesco,

I care about it ...

Andrei.

> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Donnerstag, 31. Januar 2013 12:50
> To: dev@syncope.apache.org
> Subject: Re: svn commit: r1440904 - in /syncope/trunk: build-
> tools/src/main/resources/org/apache/syncope/
> client/src/main/java/org/apache/syncope/client/services/proxy/
> common/src/main/java/org/apache/syncope/common/services/
> common/src/main/java/org/apache/syn...
> 
> Hi Andrei,
> as stated by latest failures on Jenkins, it seems that your commit broke the
> build, in particular your modification to
> core/src/main/resources/restContent.xml adds a reference to
> workflowServiceImpl that cannot be resolved by Spring.
> 
> Have you forgotten to commit something else or just to run the testsuite
> before committing? ;-)
> 
> I have just reverted this change to make the build succeed again (at least on
> JDK 1.6, but this is another story...): if you still need it, please take 
> care that
> everything is still working before committing.
> 
> Regards.
> 
> 
> On 31/01/2013 11:58, ashaki...@apache.org wrote:
> > Author: ashakirin
> > Date: Thu Jan 31 10:58:31 2013
> > New Revision: 1440904
> >
> > URL: http://svn.apache.org/viewvc?rev=1440904&view=rev
> > Log:
> > [SYNCOPE-231] Added WorkflowServiceImpl and Test
> >
> > Modified:
> >  syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/checkstyle.xml
> >
> syncope/trunk/client/src/main/java/org/apache/syncope/client/services/pr
> oxy/WorkflowServiceProxy.java
> >
> syncope/trunk/common/src/main/java/org/apache/syncope/common/servi
> ces/WorkflowService.java
> >
> syncope/trunk/common/src/main/java/org/apache/syncope/common/util/
> CollectionWrapper.java
> >
> syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/N
> otificationRestClient.java
> >
> syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/W
> orkflowRestClient.java
> >  syncope/trunk/core/src/main/resources/restContext.xml
> >
> >
> syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/Workflow
> > TestITCase.java
> >
> > Modified:
> > syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/checks
> > tyle.xml
> > URL:
> > http://svn.apache.org/viewvc/syncope/trunk/build-tools/src/main/resour
> >
> ces/org/apache/syncope/checkstyle.xml?rev=1440904&r1=1440903&r2=1440
> 90
> > 4&view=diff
> >
> ==
> 
> > 
> > ---
> > syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/checks
> > tyle.xml (original)
> > +++ syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/ch
> > +++ eckstyle.xml Thu Jan 31 10:58:31 2013
> > @@ -177,7 +177,7 @@ under the License.
> >   
> >   
> >   
> > -
> > + >
> >   
> >   
> >   
> >
> > Modified:
> > syncope/trunk/client/src/main/java/org/apache/syncope/client/services/
> > proxy/WorkflowServiceProxy.java
> > URL:
> > http://svn.apache.org/viewvc/syncope/trunk/client/src/main/java/org/ap
> >
> ache/syncope/client/services/proxy/WorkflowServiceProxy.java?rev=14409
> > 04&r1=1440903&r2=1440904&view=diff
> >
> ==
> 
> > 
> > ---
> > syncope/trunk/client/src/main/java/org/apache/syncope/client/services/
> > proxy/WorkflowServiceProxy.java (original)
> > +++ syncope/trunk/client/src/main/java/org/apache/syncope/client/servi
> > +++ ces/proxy/WorkflowServiceProxy.java Thu Jan 31 10:58:31 2013
> > @@ -22,6 +22,7 @@ import java.util.Arrays;
> >   import java.util.List;
> >   import org.apache.syncope.common.services.WorkflowService;
> >   import org.apache.syncope.common.to.WorkflowDefinitionTO;
> > +import org.apache.syncope.common.types.AttributableType;
> >   import org.springframework.web.client.RestTemplate;
> >
> >   public class WorkflowServiceProxy extends SpringServiceProxy
> > implements WorkflowService { @@ -31,17 +32,19 @@ public class
> WorkflowServiceProxy extend
> >   }
> >
> >   @Override
> > -public WorkflowDefinitionTO getDefinition(final String type) {
> > -return getRestTemplate().getForObject(baseUrl +
> "workflow/definition/" + type, WorkflowDefinitionTO.class);
> > +public WorkflowDefinitionTO getDefinition(final AttributableType type)
> {
> > +return getRestTemplate().getForObject(baseUrl +
> "workflow/definition/" + type.name().toLowerCase(),
> > +WorkflowDefinitionTO.class);
> >   }
> >
> >   @Override
> > -public void updateDefinition(final String type, final
> WorkflowDefinitionTO definition) {
> > -getRestTemplate().put(baseUrl + "workflow/definition/" + type,
> definition);
> > +public void updateDefinition(final AttributableType type, final
> WorkflowDefinitionTO definition) {
> > +getRestTemplate().put(baseUrl + "workflow/definition/" +
> > + type.name().toLowerCase(), de

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

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated SYNCOPE-297:


Attachment: syncope-297.patch

Hi guys,

I'd like some feedback on the attached patch. It does two things:

a) Removes the external attribute values for AccountId/Passwords in the 
MappingTO class (ignored by core anyway)
b) Disables the ext attr dropdown list when it's an account id or password

This fixes the problem reported in the JIRA. I've run into a similar problem 
though. If you edit the user mappings, and de-select the AccountId checkbox and 
click on the extr attribute dropdown list (but don't select a value, just click 
on it), and then re-click on AccountId, you get a "extAttrName is required" 
error message. Any ideas?

Colm.

> 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
>Assignee: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: Screenshot.png, syncope-297.patch
>
>
> 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: r1440904 - in /syncope/trunk: build-tools/src/main/resources/org/apache/syncope/ client/src/main/java/org/apache/syncope/client/services/proxy/ common/src/main/java/org/apache/syncope/

[Andrei Shakirin]

Hi,

Found ... explore SVN client required to add new files explicitly.
All tests including console were successful, but two most important file was 
not committed, super :(
Will use command line client only in the future.

Regards,
Andrei.


> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Donnerstag, 31. Januar 2013 12:50
> To: dev@syncope.apache.org
> Subject: Re: svn commit: r1440904 - in /syncope/trunk: build-
> tools/src/main/resources/org/apache/syncope/
> client/src/main/java/org/apache/syncope/client/services/proxy/
> common/src/main/java/org/apache/syncope/common/services/
> common/src/main/java/org/apache/syn...
> 
> Hi Andrei,
> as stated by latest failures on Jenkins, it seems that your commit broke the
> build, in particular your modification to
> core/src/main/resources/restContent.xml adds a reference to
> workflowServiceImpl that cannot be resolved by Spring.
> 
> Have you forgotten to commit something else or just to run the testsuite
> before committing? ;-)
> 
> I have just reverted this change to make the build succeed again (at least on
> JDK 1.6, but this is another story...): if you still need it, please take 
> care that
> everything is still working before committing.
> 
> Regards.
> 
> 
> On 31/01/2013 11:58, ashaki...@apache.org wrote:
> > Author: ashakirin
> > Date: Thu Jan 31 10:58:31 2013
> > New Revision: 1440904
> >
> > URL: http://svn.apache.org/viewvc?rev=1440904&view=rev
> > Log:
> > [SYNCOPE-231] Added WorkflowServiceImpl and Test
> >
> > Modified:
> >  syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/checkstyle.xml
> >
> syncope/trunk/client/src/main/java/org/apache/syncope/client/services/pr
> oxy/WorkflowServiceProxy.java
> >
> syncope/trunk/common/src/main/java/org/apache/syncope/common/servi
> ces/WorkflowService.java
> >
> syncope/trunk/common/src/main/java/org/apache/syncope/common/util/
> CollectionWrapper.java
> >
> syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/N
> otificationRestClient.java
> >
> syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/W
> orkflowRestClient.java
> >  syncope/trunk/core/src/main/resources/restContext.xml
> >
> >
> syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/Workflow
> > TestITCase.java
> >
> > Modified:
> > syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/checks
> > tyle.xml
> > URL:
> > http://svn.apache.org/viewvc/syncope/trunk/build-tools/src/main/resour
> >
> ces/org/apache/syncope/checkstyle.xml?rev=1440904&r1=1440903&r2=1440
> 90
> > 4&view=diff
> >
> ==
> 
> > 
> > ---
> > syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/checks
> > tyle.xml (original)
> > +++ syncope/trunk/build-
> tools/src/main/resources/org/apache/syncope/ch
> > +++ eckstyle.xml Thu Jan 31 10:58:31 2013
> > @@ -177,7 +177,7 @@ under the License.
> >   
> >   
> >   
> > -
> > + >
> >   
> >   
> >   
> >
> > Modified:
> > syncope/trunk/client/src/main/java/org/apache/syncope/client/services/
> > proxy/WorkflowServiceProxy.java
> > URL:
> > http://svn.apache.org/viewvc/syncope/trunk/client/src/main/java/org/ap
> >
> ache/syncope/client/services/proxy/WorkflowServiceProxy.java?rev=14409
> > 04&r1=1440903&r2=1440904&view=diff
> >
> ==
> 
> > 
> > ---
> > syncope/trunk/client/src/main/java/org/apache/syncope/client/services/
> > proxy/WorkflowServiceProxy.java (original)
> > +++ syncope/trunk/client/src/main/java/org/apache/syncope/client/servi
> > +++ ces/proxy/WorkflowServiceProxy.java Thu Jan 31 10:58:31 2013
> > @@ -22,6 +22,7 @@ import java.util.Arrays;
> >   import java.util.List;
> >   import org.apache.syncope.common.services.WorkflowService;
> >   import org.apache.syncope.common.to.WorkflowDefinitionTO;
> > +import org.apache.syncope.common.types.AttributableType;
> >   import org.springframework.web.client.RestTemplate;
> >
> >   public class WorkflowServiceProxy extends SpringServiceProxy
> > implements WorkflowService { @@ -31,17 +32,19 @@ public class
> WorkflowServiceProxy extend
> >   }
> >
> >   @Override
> > -public WorkflowDefinitionTO getDefinition(final String type) {
> > -return getRestTemplate().getForObject(baseUrl +
> "workflow/definition/" + type, WorkflowDefinitionTO.class);
> > +public WorkflowDefinitionTO getDefinition(final AttributableType type)
> {
> > +return getRestTemplate().getForObject(baseUrl +
> "workflow/definition/" + type.name().toLowerCase(),
> > +WorkflowDefinitionTO.class);
> >   }
> >
> >   @Override
> > -public void updateDefinition(final String type, final
> WorkflowDefinitionTO definition) {
> > -getRestTemplate().put(baseUrl + "workflow/definition/" + type,
> definition);
> > +public v

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

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #43 (See 
[https://builds.apache.org/job/Syncope-trunk/43/])
[SYNCOPE-231] Added WorkflowServiceImpl and Test (Revision 1440904)
[SYNCOPE-231]
* adding missing JAX-RS Tests (Revision 1440902)

 Result = SUCCESS
ashakirin : 
Files : 
* 
/syncope/trunk/build-tools/src/main/resources/org/apache/syncope/checkstyle.xml
* 
/syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/util/CollectionWrapper.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/NotificationRestClient.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/WorkflowRestClient.java
* /syncope/trunk/core/src/main/resources/restContext.xml
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java

jbernhardt : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/DerivedSchemaTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/SearchTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/TaskTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/UserTestITCaseJAXRS.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/VirtualSchemaTestITCaseJAXRS.java


> 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-302) Error when accessing the Resources page as non-admin

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567580#comment-13567580
 ] 

Hudson commented on SYNCOPE-302:


Integrated in Syncope-trunk #43 (See 
[https://builds.apache.org/job/Syncope-trunk/43/])
[SYNCOPE-302] Fix (Revision 1440901)

 Result = SUCCESS
ilgrosso : 
Files : 
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ConnObjectTO.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ResourceTO.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientCompositeErrorException.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Resources.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/ResourceDataBinder.java


> Error when accessing the Resources page as non-admin
> 
>
> Key: SYNCOPE-302
> URL: https://issues.apache.org/jira/browse/SYNCOPE-302
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 1.1.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
>
> When accessing the Resources page as plain user, a Stacktrace (403 Forbidden) 
> is thrown.

--
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

Syncope-trunk - Build # 43 - Fixed

[Apache Jenkins Server]

The Apache Jenkins build system has built Syncope-trunk (build #43)

Status: Fixed

Check console output at https://builds.apache.org/job/Syncope-trunk/43/ to view 
the results.

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

[JIRA]

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

Francesco Chicchiriccò resolved SYNCOPE-128.


Resolution: Fixed

Hi Denis,
I've made some rework around your original page and split in two different 
pages for user requests (including self-registration) [1] and user approval [2].

Thanks!

[1] 
https://cwiki.apache.org/confluence/display/SYNCOPE/Handle+user+requests+(including+self+registration)
[2] https://cwiki.apache.org/confluence/display/SYNCOPE/Work+with+user+approval

> 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-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #44 (See 
[https://builds.apache.org/job/Syncope-trunk/44/])
SYNCOPE-231 Fixing RoleTest (Revision 1440928)
[SYNCOPE-231] Fixed broken build (Revision 1440923)

 Result = SUCCESS
cschneider : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ReportTestITCase.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java

ashakirin : 
Files : 
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/services/WorkflowServiceImpl.java
* /syncope/trunk/core/src/main/resources/restContext.xml
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/WorkflowTestITCaseJAXRS.java


> 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-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings

[JIRA]

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

Francesco Chicchiriccò commented on SYNCOPE-297:


Hi Colm,
your patch looks fine.

About the problem you highlight above, I've experienced the same - only when 
extAttrName is dropdown - and also played a bit, unfortunately with no luck.

Finally, I was expecting that when checking 'AccountId' the mandatory condition 
text box was automatically set to 'true': am I wrong?

> 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
>Assignee: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: Screenshot.png, syncope-297.patch
>
>
> 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] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #46 (See 
[https://builds.apache.org/job/Syncope-trunk/46/])
SYNCOPE-231 Fixing create issues in PolicyTestITCase and authorization 
issue in UserTestITCase (Revision 1440971)

 Result = SUCCESS
cschneider : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/PolicyTestITCase.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java


> 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] [Updated] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-297:
---

Attachment: syncope-297-ilgrosso.patch

I've made some further investigation together with Fabio and we should have 
solved the dropdown problem.

I'm adding a patch (that include yours) - sorry if there is some non-necessary 
modification (formatting, removing unchecked calls).

> 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
>Assignee: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: Screenshot.png, syncope-297-ilgrosso.patch, 
> syncope-297.patch
>
>
> 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] [Commented] (SYNCOPE-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh commented on SYNCOPE-297:
-

Hi Francesco,

Great thanks - I'll review + apply it. I'll merge the mandatory condition thing 
separately.

Colm.

> 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
>Assignee: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: Screenshot.png, syncope-297-ilgrosso.patch, 
> syncope-297.patch
>
>
> 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

[DISCUSS] Two Jira issues for Exceptions

[Andrei Shakirin]

Hi,

We have implemented two proposals from [1] by CXF migration.
I am going to create Jira  issues for rest two:

1)  Mapping to SyncopeClientCompositeException on client side

2)  Mapping low level exceptions in core

and schedule them to 1.3.0?

Any objections?

Regards,
Andrei.

[1] https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions

Re: [DISCUSS] Two Jira issues for Exceptions

[Francesco Chicchiriccò]

On 31/01/2013 15:54, Andrei Shakirin wrote:

Hi,

We have implemented two proposals from [1] by CXF migration.
I am going to create Jira  issues for rest two:

1)  Mapping to SyncopeClientCompositeException on client side

2)  Mapping low level exceptions in core


Fine.


and schedule them to 1.3.0?


Why not 1.2.0?

Regards.


[1] https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions


--
Francesco Chicchiriccò

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

RE: [DISCUSS] Two Jira issues for Exceptions

[Jan Bernhardt]

> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Donnerstag, 31. Januar 2013 15:58
> To: dev@syncope.apache.org
> Subject: Re: [DISCUSS] Two Jira issues for Exceptions
> 
> On 31/01/2013 15:54, Andrei Shakirin wrote:
> > Hi,
> >
> > We have implemented two proposals from [1] by CXF migration.
> > I am going to create Jira  issues for rest two:
> >
> > 1)  Mapping to SyncopeClientCompositeException on client side
> >
> > 2)  Mapping low level exceptions in core
> 

+1

> Fine.
> 
> > and schedule them to 1.3.0?
> 
> Why not 1.2.0?

+1 for 1.2.0

> 
> Regards.
> 
> > [1]
> >
> https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions
> 
> --
> Francesco Chicchiriccò
> 
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/

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

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-298:


Integrated in Syncope-trunk #47 (See 
[https://builds.apache.org/job/Syncope-trunk/47/])
Added comments to non re-runnable test and workaround for SYNCOPE-298 
(Revision 1441004)

 Result = SUCCESS
ashakirin : 
Files : 
* 
/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


> 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-297) External Attributes are showing up for AccoundId/Password in Resource User Mappings

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh resolved SYNCOPE-297.
-

Resolution: Fixed

> 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
>Assignee: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: Screenshot.png, syncope-297-ilgrosso.patch, 
> syncope-297.patch
>
>
> 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-303) Mapping to SyncopeClientCompositeException on client side

[Andrei Shakirin (JIRA)]

Andrei Shakirin created SYNCOPE-303:
---

 Summary: Mapping to SyncopeClientCompositeException on client side
 Key: SYNCOPE-303
 URL: https://issues.apache.org/jira/browse/SYNCOPE-303
 Project: Syncope
  Issue Type: Improvement
  Components: common, core
Reporter: Andrei Shakirin
 Fix For: 1.2.0


Actually almost all exceptions with status BAD_REQUEST and NOT_FOUND are mapped 
to SyncopeClientCompositeErrorException on the client side.
It is absolutely OK for composite exceptions containing number of 
sub-exceptions (like validation and propagation), however for some single 
exceptions it makes more sense to map not to 
SyncopeClientCompositeErrorException, but directly to corresponded exception 
type.
Candidates are:

Deadlock
ExistingResource
DataIntegrityViolation
GenericPersistence
UnauthorizedRole

Proposed mapping makes exception processing more easy and effective.

https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions

--
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-304) Mapping low level exceptions in core

[Andrei Shakirin (JIRA)]

Andrei Shakirin created SYNCOPE-304:
---

 Summary: Mapping low level exceptions in core
 Key: SYNCOPE-304
 URL: https://issues.apache.org/jira/browse/SYNCOPE-304
 Project: Syncope
  Issue Type: Improvement
  Components: core
Reporter: Andrei Shakirin
 Fix For: 1.2.0


Actually service layer processes three relative low level exceptions from 
persistence:

org.apache.ibatis.exceptions.PersistenceException;
org.springframework.orm.jpa.JpaSystemException;
javax.persistence.PersistenceException

Suggestion: abstract service implementation from persistence a little bit more 
and wrap these three exceptions in high level Syncope PersistenceException.
>From my perspective it helps for the cases when Syncope will support 
>alternative persistence technologies like Hibernate JPA, EclipseLink JPA or 
>even LDAP, JCR, non-SQL DBs.

https://cwiki.apache.org/confluence/display/SYNCOPE/Remote+Exceptions

--
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

Another Console error

[Colm O hEigeartaigh]

Hi guys,

I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
scenario here is the propagation of a user with a simple User attribute to
a backend. If I enter the attribute without hitting 'enter' it propagates
fine. If I create another user, enter the value for the attribute + hit
enter, then go on to select the resource etc., I get an error message
saying that "'Schema' is required".

Any ideas on what might be causing this?

Colm.


-- 
Colm O hEigeartaigh

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

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

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-297:


Integrated in Syncope-trunk #48 (See 
[https://builds.apache.org/job/Syncope-trunk/48/])
[SYNCOPE-297] - External Attributes are showing up for AccoundId/Password 
in Resource User Mappings
 - Applying Francesco's modified version of my patch (Revision 1441037)

 Result = SUCCESS
coheigea : 
Files : 
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/MappingTO.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/AjaxCheckBoxPanel.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/AjaxDropDownChoicePanel.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/FieldPanel.java


> 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
>Assignee: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: Screenshot.png, syncope-297-ilgrosso.patch, 
> syncope-297.patch
>
>
> 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] [Commented] (SYNCOPE-231) Using Standard JAX-RS API in Syncope (Introducing Apache CXF WS Stack)

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #48 (See 
[https://builds.apache.org/job/Syncope-trunk/48/])
SYNCOPE-231 Activate TaskTest (Revision 1441029)
SYNCOPE-231 Simplified PolicyService and TaskService (Revision 1441024)
[SYNCOPE-231]
* adding JAVA DOC for Service Interfaces
* Code cleanup (Revision 1441023)

 Result = SUCCESS
cschneider : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/TaskTestITCaseJAXRS.java

cschneider : 
Files : 
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/PolicyController.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/TaskController.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/services/PolicyServiceImpl.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/services/TaskServiceImpl.java

jbernhardt : 
Files : 
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/SchemaService.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserRequestService.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/to/WorkflowDefinitionTO.java


> 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: Another Console error

[Francesco Chicchiriccò]

On 31/01/2013 17:28, Colm O hEigeartaigh wrote:

Hi guys,

I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
scenario here is the propagation of a user with a simple User attribute to
a backend. If I enter the attribute without hitting 'enter' it propagates
fine. If I create another user, enter the value for the attribute + hit
enter, then go on to select the resource etc., I get an error message
saying that "'Schema' is required".

Any ideas on what might be causing this?


Hi Colm,
it sounds like the same problem we fixed in SYNCOPE-297, i.e. basically 
a partial Ajax submit that should be avoided (as the patch for 
SYNCOPE-297 did).


However, I am not sure to understand exactly how to replicate this: are 
you creating an user and hitting enter when populating attribute values? 
If so, I guess this happens with roles as well, isn’t it?


Another possibility might simply be that enter is key-bound to form 
submit...


Regards.

--
Francesco Chicchiriccò

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

Re: Another Console error

[Colm O hEigeartaigh]

Hi Francesco,

> However, I am not sure to understand exactly how to replicate this: are
you creating an user and hitting enter when populating attribute
> values? If so, I guess this happens with roles as well, isn’t it?

Yep exactly. Fill in username + password, enter some random string for an
attribute + hit enter in the textbox when done. Then continue + select
resource, and finally hit "submit". It works when I don't hit enter on the
attribute, and fails when I do. I haven't tried with roles.

> Another possibility might simply be that enter is key-bound to form
submit...

Possibly, although it doesn't try to submit straight away. The error crops
up when I click on "submit".

Thanks,

Colm.

On Thu, Jan 31, 2013 at 4:40 PM, Francesco Chicchiriccò  wrote:

> On 31/01/2013 17:28, Colm O hEigeartaigh wrote:
>
>> Hi guys,
>>
>> I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
>> scenario here is the propagation of a user with a simple User attribute to
>> a backend. If I enter the attribute without hitting 'enter' it propagates
>> fine. If I create another user, enter the value for the attribute + hit
>> enter, then go on to select the resource etc., I get an error message
>> saying that "'Schema' is required".
>>
>> Any ideas on what might be causing this?
>>
>
> Hi Colm,
> it sounds like the same problem we fixed in SYNCOPE-297, i.e. basically a
> partial Ajax submit that should be avoided (as the patch for SYNCOPE-297
> did).
>
> However, I am not sure to understand exactly how to replicate this: are
> you creating an user and hitting enter when populating attribute values? If
> so, I guess this happens with roles as well, isn’t it?
>
> Another possibility might simply be that enter is key-bound to form
> submit...
>
> Regards.
>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~**ilgrosso/
>
>


-- 
Colm O hEigeartaigh

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

Re: Another Console error

[Francesco Chicchiriccò]

On 31/01/2013 17:44, Colm O hEigeartaigh wrote:

Hi Francesco,


However, I am not sure to understand exactly how to replicate this: are you 
creating an user and hitting enter when populating attribute values? If so, I 
guess this happens with roles as well, isn’t it?

Yep exactly. Fill in username + password, enter some random string for an
attribute + hit enter in the textbox when done. Then continue + select
resource, and finally hit "submit". It works when I don't hit enter on the
attribute, and fails when I do. I haven't tried with roles.


Another possibility might simply be that enter is key-bound to form submit...

Possibly, although it doesn't try to submit straight away. The error crops
up when I click on "submit".


Colm,
I was trying to replicate this misbehavior with Chrome without any luck 
because hitting Enter just caused the whole form to submit (as said), 
then I moved to Firefox and replicated the same problem.


By doing so I have noticed that the number of warnings ('Schema' is 
required) was the same as empty derived attributes that resulted added 
under the respective tab.


So, this must be the issue: with Chrome, Enter submits the whole form, 
with Firefox instead the "Add" button in the derived attributes tab is 
triggered. Odd...


Do you have an idea about how to fix this?

Regards.


On Thu, Jan 31, 2013 at 4:40 PM, Francesco Chicchiriccò 
wrote:
On 31/01/2013 17:28, Colm O hEigeartaigh wrote:


Hi guys,

I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
scenario here is the propagation of a user with a simple User attribute to
a backend. If I enter the attribute without hitting 'enter' it propagates
fine. If I create another user, enter the value for the attribute + hit
enter, then go on to select the resource etc., I get an error message
saying that "'Schema' is required".

Any ideas on what might be causing this?


Hi Colm,
it sounds like the same problem we fixed in SYNCOPE-297, i.e. basically a
partial Ajax submit that should be avoided (as the patch for SYNCOPE-297
did).

However, I am not sure to understand exactly how to replicate this: are
you creating an user and hitting enter when populating attribute values? If
so, I guess this happens with roles as well, isn’t it?

Another possibility might simply be that enter is key-bound to form
submit...

Regards.


--
Francesco Chicchiriccò

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

Re: Build not working (again) with JDK 1.7

[Francesco Chicchiriccò]

Hi Andrei,
I just want to report that, after today's work, I am able to 
successfully build with JDK 1.7 -  I guess you've found the way to cope 
with existing ids in the test content.xml and the ids generated during 
test execution, nice!


Regards.

On 30/01/2013 13:43, Andrei Shakirin wrote:

Hi Francesco,

I have problem under jdk 1.7 as well, but in other test!

Running org.apache.syncope.core.rest.UserTestITCase
Tests run: 52, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 33.524 sec <<<
FAILURE!
testEnforceMandatoryConditionOnDerived(org.apache.syncope.core.rest.UserTestITCa
se)  Time elapsed: 0.172 sec  <<< ERROR!
org.apache.syncope.common.validation.SyncopeClientCompositeErrorException: {[Dat
aIntegrityViolation [The transaction has been rolled back.  See the nested excep
tions for details on the errors that occurred.]]}

This problem is really related to SYNCOPE-298:

SEVERE: Servlet.service() for servlet [syncope-core-rest] in context with path 
[/syncope] threw exception [Request processing failed; nested exception is 
org.springframework.dao.DataIntegrityViolationException: The transaction has been 
rolled back.  See the nested exceptions for details on the errors that occurred.; 
nested exception is  
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@3aa73b72] 
with root cause
org.apache.openjpa.lib.jdbc.ReportingSQLException: 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 178787393 INSERT INTO PUBLIC.UVirAttr (ID, OWNER_ID, 
VIRTUALSCHEMA_NAME) VALUES (?, ?, ?)} [code=23505, state=23505]
at 
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:219)
at 
org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:195)

Could you please experiment a little bit in your environment:
1. Check cargo-output.log for 
org.apache.openjpa.persistence.EntityExistsException related to 
org.apache.syncope.core.persistence.beans.user.UVirAttr
2. Run UserTestITCase and TaskITTestCase separately and check if problems are 
still there.
?

Let see if it will be necessary to re-prioritize SYNCOPE-298.

Regards,
Andrei.

P.S: Task patch from SYNCOPE-231 has inserted @Ignored to 2 TaskTestITCase 
tests. I will care to enable them again.


-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Mittwoch, 30. Januar 2013 11:41
To: dev@syncope.apache.org
Subject: Build not working (again) with JDK 1.7

Hi all,
unfortunately, after latest updates since yesterday afternoon when I did my
last checks, the build on JDK 1.7 is failing again:

Results :

Failed tests:
UserTestITCase.create:481 expected:<166> but was:<165>
UserTestITCase.verifyTaskRegistration:1000 expected:<187> but was:<186>

Tests in error:
TaskTestITCase.sync:325 » SyncopeClientCompositeError {[NotFound [User
test0]]...


With JDK 1.6 no problems (as Jenkins confirms).

Both behaviours seems to be stable.

Andrei told me yesterday that this is not the case, but just for sake of
completeness, let's think again if this is related to SYNCOPE-298.

If not, what can be the reason of these failures with JDK 1.7?

Regards.

--
Francesco Chicchiriccò

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


--
Francesco Chicchiriccò

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

Re: Open Wiki pages for CXF migration

[Francesco Chicchiriccò]

On 30/01/2013 08:43, Francesco Chicchiriccò wrote:

On 30/01/2013 08:41, Jan Bernhardt wrote:

Hi Francesco,

Yes, I will take care of this. It was on my agenda to update 
documentation site by today.


Great, thank you Jan.


Jan,
"TODO: Is this a good design decision? Should these activities be moved 
to WorkflowController?" is still on the page - is it by purpose?


Regards.


-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Mittwoch, 30. Januar 2013 08:30
To: dev@syncope.apache.org
Subject: Re: Open Wiki pages for CXF migration

On 28/01/2013 11:49, Francesco Chicchiriccò wrote:

Done.

Please remove any personal annotation from the wiki page (like as
"TODO: Is this a good design decision? Should these activities be
moved to WorkflowController?" or "In the near feature I would also
like to replace the current search NodeCond with FIQL searchqueries.")
and convert such items to issues / e-mails.
Thanks.

Any maintainer of this page available to perform such actions?


On 24/01/2013 14:17, Jan Bernhardt wrote:

+1

Best regards.
Jan



-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Donnerstag, 24. Januar 2013 12:40
To: dev@syncope.apache.org
Subject: Re: Open Wiki pages for CXF migration

On 23/01/2013 15:33, Christian Schneider wrote:

Hi Syncopers,

the wiki pages about the rest api and the exception concept are
currently protected. I can not access them and as Francesco
reported some time ago we can not directly edit the group that
protects the page.
So I propose to open these pages for the public and simply have a
disclaimer that this is work in progress.

See:


https://cwiki.apache.org/confluence/display/SYNCOPE/REST+API+upgrad

e

Agree: If no one has objections, I would unlock access to that wiki
page (and its children) + add a disclaimer.

Regards.





--
Francesco Chicchiriccò

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

[jira] [Commented] (SYNCOPE-210) Provide suggestions / help / examples for JEXL-based input fields

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567853#comment-13567853
 ] 

Hudson commented on SYNCOPE-210:


Integrated in Syncope-trunk #49 (See 
[https://builds.apache.org/job/Syncope-trunk/49/])
SYNCOPE-210 Jexl syntax help added (Revision 1441074)

 Result = SUCCESS
massi : 
Files : 
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeApplication.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/JexlHelpUtil.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/DerivedSchemaModalPage.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/AttributesPanel.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/DerivedSchemaModalPage.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/DerivedSchemaModalPage.properties
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/DerivedSchemaModalPage_it.properties
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/AttributesPanel.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/AttributesPanel.properties
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/AttributesPanel_it.properties
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/ResourceMappingPanel.html
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/ResourceMappingPanel.properties
* 
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/ResourceMappingPanel_it.properties
* /syncope/trunk/console/src/main/webapp/css/style.css
* /syncope/trunk/console/src/main/webapp/img/help.png


> Provide suggestions / help / examples for JEXL-based input fields
> -
>
> Key: SYNCOPE-210
> URL: https://issues.apache.org/jira/browse/SYNCOPE-210
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: Massimiliano Perrone
> Fix For: 1.1.0
>
> Attachments: one.png, two.png
>
>
> There are many input text fields accepting JEXL syntax:
>  * derived schema definition (user / role / membership)
>  * values for defining synchronization user template
>  * schema mapping's mandatory condition
>  * ...
> Users would benefit from some examples, help, suggestions, link to JEXL 
> reference to be displayed in (or linked from) the web forms containing such 
> input fields.

--
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)

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-231:


Integrated in Syncope-trunk #49 (See 
[https://builds.apache.org/job/Syncope-trunk/49/])
SYNCOPE-231 Fix for rerun issue on user deletion (Revision 1441052)
[SYNCOPE-231] Enabled JAXRS TaskTestITCase (Revision 1441050)

 Result = SUCCESS
cschneider : 
Files : 
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java

ashakirin : 
Files : 
* /syncope/trunk/core/src/main/resources/restContext.xml
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/jaxrs/TaskTestITCaseJAXRS.java


> 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] [Resolved] (SYNCOPE-210) Provide suggestions / help / examples for JEXL-based input fields

[Massimiliano Perrone (JIRA)]

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

Massimiliano Perrone resolved SYNCOPE-210.
--

Resolution: Fixed

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

> Provide suggestions / help / examples for JEXL-based input fields
> -
>
> Key: SYNCOPE-210
> URL: https://issues.apache.org/jira/browse/SYNCOPE-210
> Project: Syncope
>  Issue Type: Improvement
>  Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: Massimiliano Perrone
> Fix For: 1.1.0
>
> Attachments: one.png, two.png
>
>
> There are many input text fields accepting JEXL syntax:
>  * derived schema definition (user / role / membership)
>  * values for defining synchronization user template
>  * schema mapping's mandatory condition
>  * ...
> Users would benefit from some examples, help, suggestions, link to JEXL 
> reference to be displayed in (or linked from) the web forms containing such 
> input fields.

--
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-295) If AccountId is selected when creating a Resource Mapping, then make it mandatory

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh resolved SYNCOPE-295.
-

Resolution: Fixed

> If AccountId is selected when creating a Resource Mapping, then make it 
> mandatory
> -
>
> Key: SYNCOPE-295
> URL: https://issues.apache.org/jira/browse/SYNCOPE-295
> Project: Syncope
>  Issue Type: Improvement
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 1.1.0
>
>
> If AccountId is selected when creating a Resource Mapping, then make it 
> mandatory + remove the ability to edit the Mandatory field. As an Account Id 
> mapping is always mandatory, then this makes creating new resource mappings 
> slightly quicker.

--
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: Another Console error

[Colm O hEigeartaigh]

Hi Francesco,

> So, this must be the issue: with Chrome, Enter submits the whole form,
with Firefox instead the "Add" button in the derived attributes > tab is
triggered. Odd...

Cool, that's the error alright (on Firefox). Hitting 'enter' in either a
attribute or virtual attribute textbox causes an extra derived attribute
entry to be added! I'll take a look and see what's going on.

Colm.

On Thu, Jan 31, 2013 at 4:59 PM, Francesco Chicchiriccò  wrote:

> On 31/01/2013 17:44, Colm O hEigeartaigh wrote:
>
>> Hi Francesco,
>>
>>  However, I am not sure to understand exactly how to replicate this: are
>>> you creating an user and hitting enter when populating attribute values? If
>>> so, I guess this happens with roles as well, isn’t it?
>>>
>> Yep exactly. Fill in username + password, enter some random string for an
>> attribute + hit enter in the textbox when done. Then continue + select
>> resource, and finally hit "submit". It works when I don't hit enter on the
>> attribute, and fails when I do. I haven't tried with roles.
>>
>>  Another possibility might simply be that enter is key-bound to form
>>> submit...
>>>
>> Possibly, although it doesn't try to submit straight away. The error crops
>> up when I click on "submit".
>>
>
> Colm,
> I was trying to replicate this misbehavior with Chrome without any luck
> because hitting Enter just caused the whole form to submit (as said), then
> I moved to Firefox and replicated the same problem.
>
> By doing so I have noticed that the number of warnings ('Schema' is
> required) was the same as empty derived attributes that resulted added
> under the respective tab.
>
> So, this must be the issue: with Chrome, Enter submits the whole form,
> with Firefox instead the "Add" button in the derived attributes tab is
> triggered. Odd...
>
> Do you have an idea about how to fix this?
>
> Regards.
>
>
>  On Thu, Jan 31, 2013 at 4:40 PM, Francesco Chicchiriccò <
>> ilgro...@apache.org
>>
>>> wrote:
>>> On 31/01/2013 17:28, Colm O hEigeartaigh wrote:
>>>
>>>  Hi guys,

 I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
 scenario here is the propagation of a user with a simple User attribute
 to
 a backend. If I enter the attribute without hitting 'enter' it
 propagates
 fine. If I create another user, enter the value for the attribute + hit
 enter, then go on to select the resource etc., I get an error message
 saying that "'Schema' is required".

 Any ideas on what might be causing this?

  Hi Colm,
>>> it sounds like the same problem we fixed in SYNCOPE-297, i.e. basically a
>>> partial Ajax submit that should be avoided (as the patch for SYNCOPE-297
>>> did).
>>>
>>> However, I am not sure to understand exactly how to replicate this: are
>>> you creating an user and hitting enter when populating attribute values?
>>> If
>>> so, I guess this happens with roles as well, isn’t it?
>>>
>>> Another possibility might simply be that enter is key-bound to form
>>> submit...
>>>
>>> Regards.
>>>
>>
> --
> Francesco Chicchiriccò
>
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~**ilgrosso/
>
>


-- 
Colm O hEigeartaigh

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

[jira] [Commented] (SYNCOPE-295) If AccountId is selected when creating a Resource Mapping, then make it mandatory

[Hudson (JIRA)]

[ 
https://issues.apache.org/jira/browse/SYNCOPE-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13567995#comment-13567995
 ] 

Hudson commented on SYNCOPE-295:


Integrated in Syncope-trunk #50 (See 
[https://builds.apache.org/job/Syncope-trunk/50/])
[SYNCOPE-295] - If AccountId is selected when creating a Resource Mapping, 
then make it mandatory (Revision 1441087)

 Result = SUCCESS
coheigea : 
Files : 
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java


> If AccountId is selected when creating a Resource Mapping, then make it 
> mandatory
> -
>
> Key: SYNCOPE-295
> URL: https://issues.apache.org/jira/browse/SYNCOPE-295
> Project: Syncope
>  Issue Type: Improvement
>Reporter: Colm O hEigeartaigh
>Assignee: Colm O hEigeartaigh
>Priority: Trivial
> Fix For: 1.1.0
>
>
> If AccountId is selected when creating a Resource Mapping, then make it 
> mandatory + remove the ability to edit the Mandatory field. As an Account Id 
> mapping is always mandatory, then this makes creating new resource mappings 
> slightly quicker.

--
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: Another Console error

[Francesco Chicchiriccò]

On 31/01/2013 19:01, Colm O hEigeartaigh wrote:

Hi Francesco,


So, this must be the issue: with Chrome, Enter submits the whole form, with Firefox 
instead the "Add" button in the derived attributes tab is triggered. Odd...

Cool, that's the error alright (on Firefox). Hitting 'enter' in either a
attribute or virtual attribute textbox causes an extra derived attribute
entry to be added! I'll take a look and see what's going on.


Hi Colm,
wouldn't be enough, then, to bind the Enter key to the form submit on 
all browsers?



On Thu, Jan 31, 2013 at 4:59 PM, Francesco Chicchiriccò  
wrote:


On 31/01/2013 17:44, Colm O hEigeartaigh wrote:


Hi Francesco,

  However, I am not sure to understand exactly how to replicate this: are

you creating an user and hitting enter when populating attribute values? If
so, I guess this happens with roles as well, isn’t it?


Yep exactly. Fill in username + password, enter some random string for an
attribute + hit enter in the textbox when done. Then continue + select
resource, and finally hit "submit". It works when I don't hit enter on the
attribute, and fails when I do. I haven't tried with roles.

  Another possibility might simply be that enter is key-bound to form

submit...


Possibly, although it doesn't try to submit straight away. The error crops
up when I click on "submit".


Colm,
I was trying to replicate this misbehavior with Chrome without any luck
because hitting Enter just caused the whole form to submit (as said), then
I moved to Firefox and replicated the same problem.

By doing so I have noticed that the number of warnings ('Schema' is
required) was the same as empty derived attributes that resulted added
under the respective tab.

So, this must be the issue: with Chrome, Enter submits the whole form,
with Firefox instead the "Add" button in the derived attributes tab is
triggered. Odd...

Do you have an idea about how to fix this?

Regards.


  On Thu, Jan 31, 2013 at 4:40 PM, Francesco Chicchiriccò <

ilgro...@apache.org


wrote:
On 31/01/2013 17:28, Colm O hEigeartaigh wrote:

  Hi guys,

I'm seeing a console error on trunk somewhat similar to SYNCOPE-297. The
scenario here is the propagation of a user with a simple User attribute
to
a backend. If I enter the attribute without hitting 'enter' it
propagates
fine. If I create another user, enter the value for the attribute + hit
enter, then go on to select the resource etc., I get an error message
saying that "'Schema' is required".

Any ideas on what might be causing this?

  Hi Colm,

it sounds like the same problem we fixed in SYNCOPE-297, i.e. basically a
partial Ajax submit that should be avoided (as the patch for SYNCOPE-297
did).

However, I am not sure to understand exactly how to replicate this: are
you creating an user and hitting enter when populating attribute values?
If
so, I guess this happens with roles as well, isn’t it?

Another possibility might simply be that enter is key-bound to form
submit...

Regards.


--
Francesco Chicchiriccò

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