Re: Standalone deployment errors

[Colm O hEigeartaigh]

> Could you please try
>
> quartz.sql=tables_mysql.sql
>
> then wipe out the database content and restart Syncope?


That works, thanks! Should the wiki be updated with the above?

Colm.

On Thu, Feb 21, 2013 at 3:49 PM, Francesco Chicchiriccò  wrote:

> On 21/02/2013 16:45, Colm O hEigeartaigh wrote:
>
>>
>>  Which value do you have in core/src/main/resources/**persistence.properties
>>> for quartz.sql?
>>>
>> quartz.sql=tables_mysql_**innodb.sql
>>
>> Moreover, do you have some QRTZ_* tables in your database?
>>
>>
>> No, there are none there.
>>
>
> Could you please try
>
> quartz.sql=tables_mysql.sql
>
> then wipe out the database content and restart Syncope?
>
> Please check if you still have the Quartz error messages and no QRTZ
> tables.
>
> 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: Standalone deployment errors

[Francesco Chicchiriccò]

On 22/02/2013 10:44, Colm O hEigeartaigh wrote:

Could you please try

quartz.sql=tables_mysql.sql

then wipe out the database content and restart Syncope?

That works, thanks! Should the wiki be updated with the above?


The reason why this is working is that you seem to not have the InnoDB 
engine enabled in your MySQL instance; hence, the wiki content should be 
updated with something like: "if you have InnoDB enabled... or instead..."


Regards.


On Thu, Feb 21, 2013 at 3:49 PM, Francesco Chicchiriccò 
wrote:
On 21/02/2013 16:45, Colm O hEigeartaigh wrote:


  Which value do you have in core/src/main/resources/**persistence.properties

for quartz.sql?


quartz.sql=tables_mysql_**innodb.sql

Moreover, do you have some QRTZ_* tables in your database?


No, there are none there.


Could you please try

quartz.sql=tables_mysql.sql

then wipe out the database content and restart Syncope?

Please check if you still have the Quartz error messages and no QRTZ
tables.

Regards.


--
Francesco Chicchiriccò

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

[jira] [Created] (SYNCOPE-322) Can't create a new Role in Chromium

[Colm O hEigeartaigh (JIRA)]

Colm O hEigeartaigh created SYNCOPE-322:
---

 Summary: Can't create a new Role in Chromium
 Key: SYNCOPE-322
 URL: https://issues.apache.org/jira/browse/SYNCOPE-322
 Project: Syncope
  Issue Type: Bug
  Components: console
Reporter: Colm O hEigeartaigh
 Fix For: 1.1.0
 Attachments: chromium.png, firefox.png


If I start Syncope up with no existing roles, and navigate to the "Roles" tab, 
I can't find a way to create a new Role on Chromium. I'm attaching screenshots 
of the difference between Firefox and Chromium (on Ubuntu) - the latter is 
missing a icon to create the Role.

--
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-322) Can't create a new Role in Chromium

[Colm O hEigeartaigh (JIRA)]

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

Colm O hEigeartaigh updated SYNCOPE-322:


Attachment: firefox.png
chromium.png

> Can't create a new Role in Chromium
> ---
>
> Key: SYNCOPE-322
> URL: https://issues.apache.org/jira/browse/SYNCOPE-322
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Reporter: Colm O hEigeartaigh
> Fix For: 1.1.0
>
> Attachments: chromium.png, firefox.png
>
>
> If I start Syncope up with no existing roles, and navigate to the "Roles" 
> tab, I can't find a way to create a new Role on Chromium. I'm attaching 
> screenshots of the difference between Firefox and Chromium (on Ubuntu) - the 
> latter is missing a icon to create the Role.

--
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] REST: create turns into update for some entities

[Francesco Chicchiriccò]

Hi all,
I have recently found that some REST create requests are treated as update.

For example, try to create a new schema on the admin console and provide 
a name of another existing schema: you won't get any warning; only, the 
existing schema definition will be completely replaced by the newly 
inserted entry.


After some investigations, I've found that this happens for external 
resources, schema, derived schema and virtual schema.

Such entities have in common the fact that the JPA @Id is non-generated.
The way how saving is handled (via EntityManager#merge()) finally turns 
an expected create into an update.


I don't find such behavior as correct, hence I would propose to throw an 
exception, in the REST create methods for the entities named above, in 
case the key of the entity being created is already present.


Do you see any problem with this?

--
Francesco Chicchiriccò

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

Re: [DISCUSS] REST: create turns into update for some entities

[Fabio Martelli]

Il giorno 22/feb/2013, alle ore 12.43, Francesco Chicchiriccò ha scritto:

> Hi all,
> I have recently found that some REST create requests are treated as update.
> 
> For example, try to create a new schema on the admin console and provide a 
> name of another existing schema: you won't get any warning; only, the 
> existing schema definition will be completely replaced by the newly inserted 
> entry.
> 
> After some investigations, I've found that this happens for external 
> resources, schema, derived schema and virtual schema.
> Such entities have in common the fact that the JPA @Id is non-generated.
> The way how saving is handled (via EntityManager#merge()) finally turns an 
> expected create into an update.
> 
> I don't find such behavior as correct, hence I would propose to throw an 
> exception, in the REST create methods for the entities named above, in case 
> the key of the entity being created is already present.
> 
> Do you see any problem with this?
This sounds like a very dangerous behavior.
I do agree with the changes suggested. 

Regards,
F.

[jira] [Created] (SYNCOPE-323) REST: create turns into update for some entities

[JIRA]

Francesco Chicchiriccò created SYNCOPE-323:
--

 Summary: REST: create turns into update for some entities
 Key: SYNCOPE-323
 URL: https://issues.apache.org/jira/browse/SYNCOPE-323
 Project: Syncope
  Issue Type: Bug
  Components: core
Affects Versions: 1.0.5, 1.1.0
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
 Fix For: 1.1.0


I have recently found that some REST create requests are treated as update.

For example, try to create a new schema on the admin console and provide a name 
of another existing schema: you won't get any warning; only, the existing 
schema definition will be completely replaced by the newly inserted entry.

After some investigations, I've found that this happens for external resources, 
schema, derived schema and virtual schema.
Such entities have in common the fact that the JPA @Id is non-generated.
The way how saving is handled (via EntityManager#merge()) finally turns an 
expected create into an update.

I don't find such behavior as correct, hence I would propose to throw an 
exception, in the REST create methods for the entities named above, in case the 
key of the entity being created is already present. 

[1] http://markmail.org/message/kxrh7pgwuijwyfik

--
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] REST: create turns into update for some entities

[Francesco Chicchiriccò]

I have opened SYNCOPE-323 for this.

Regards.

On 22/02/2013 12:43, Francesco Chicchiriccò wrote:

Hi all,
I have recently found that some REST create requests are treated as 
update.


For example, try to create a new schema on the admin console and 
provide a name of another existing schema: you won't get any warning; 
only, the existing schema definition will be completely replaced by 
the newly inserted entry.


After some investigations, I've found that this happens for external 
resources, schema, derived schema and virtual schema.

Such entities have in common the fact that the JPA @Id is non-generated.
The way how saving is handled (via EntityManager#merge()) finally 
turns an expected create into an update.


I don't find such behavior as correct, hence I would propose to throw 
an exception, in the REST create methods for the entities named above, 
in case the key of the entity being created is already present.


Do you see any problem with this?


--
Francesco Chicchiriccò

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

RE: [DISCUSS] REST: create turns into update for some entities

[Andrei Shakirin]

Hi Francesco,

+1 for issue.
Find it also quite dangerous, create() should throw exception if entity already 
exists, "409 Conflict" will be corresponded HTTP error code in this case.

Regards,
Andrei.

> -Original Message-
> From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
> Sent: Freitag, 22. Februar 2013 14:44
> To: dev@syncope.apache.org
> Subject: Re: [DISCUSS] REST: create turns into update for some entities
> 
> I have opened SYNCOPE-323 for this.
> 
> Regards.
> 
> On 22/02/2013 12:43, Francesco Chicchiriccò wrote:
> > Hi all,
> > I have recently found that some REST create requests are treated as
> > update.
> >
> > For example, try to create a new schema on the admin console and
> > provide a name of another existing schema: you won't get any warning;
> > only, the existing schema definition will be completely replaced by
> > the newly inserted entry.
> >
> > After some investigations, I've found that this happens for external
> > resources, schema, derived schema and virtual schema.
> > Such entities have in common the fact that the JPA @Id is non-generated.
> > The way how saving is handled (via EntityManager#merge()) finally
> > turns an expected create into an update.
> >
> > I don't find such behavior as correct, hence I would propose to throw
> > an exception, in the REST create methods for the entities named above,
> > in case the key of the entity being created is already present.
> >
> > Do you see any problem with this?
> >
> --
> Francesco Chicchiriccò
> 
> ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
> http://people.apache.org/~ilgrosso/

[jira] [Assigned] (SYNCOPE-322) Can't create a new Role in Chromium

[JIRA]

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

Francesco Chicchiriccò reassigned SYNCOPE-322:
--

Assignee: Francesco Chicchiriccò

> Can't create a new Role in Chromium
> ---
>
> Key: SYNCOPE-322
> URL: https://issues.apache.org/jira/browse/SYNCOPE-322
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Reporter: Colm O hEigeartaigh
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
> Attachments: chromium.png, firefox.png
>
>
> If I start Syncope up with no existing roles, and navigate to the "Roles" 
> tab, I can't find a way to create a new Role on Chromium. I'm attaching 
> screenshots of the difference between Firefox and Chromium (on Ubuntu) - the 
> latter is missing a icon to create the Role.

--
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-322) Can't create a new Role in Chromium

[JIRA]

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

Francesco Chicchiriccò resolved SYNCOPE-322.


Resolution: Fixed

http://svn.apache.org/r1449078

> Can't create a new Role in Chromium
> ---
>
> Key: SYNCOPE-322
> URL: https://issues.apache.org/jira/browse/SYNCOPE-322
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Reporter: Colm O hEigeartaigh
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
> Attachments: chromium.png, firefox.png
>
>
> If I start Syncope up with no existing roles, and navigate to the "Roles" 
> tab, I can't find a way to create a new Role on Chromium. I'm attaching 
> screenshots of the difference between Firefox and Chromium (on Ubuntu) - the 
> latter is missing a icon to create the Role.

--
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-322) Can't create a new Role in Chromium

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-322:


Integrated in Syncope-trunk #107 (See 
[https://builds.apache.org/job/Syncope-trunk/107/])
[SYNCOPE-322] Fixing CSS to cope with Chrome / Chromium (Revision 1449078)

 Result = FAILURE
ilgrosso : 
Files : 
* /syncope/trunk/console/src/main/webapp/css/style.css


> Can't create a new Role in Chromium
> ---
>
> Key: SYNCOPE-322
> URL: https://issues.apache.org/jira/browse/SYNCOPE-322
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Reporter: Colm O hEigeartaigh
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
> Attachments: chromium.png, firefox.png
>
>
> If I start Syncope up with no existing roles, and navigate to the "Roles" 
> tab, I can't find a way to create a new Role on Chromium. I'm attaching 
> screenshots of the difference between Firefox and Chromium (on Ubuntu) - the 
> latter is missing a icon to create the Role.

--
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 # 107 - Failure

[Apache Jenkins Server]

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

Status: Failure

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

[jira] [Resolved] (SYNCOPE-323) REST: create turns into update for some entities

[JIRA]

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

Francesco Chicchiriccò resolved SYNCOPE-323.


Resolution: Fixed

http://svn.apache.org/r1449107

> REST: create turns into update for some entities
> 
>
> Key: SYNCOPE-323
> URL: https://issues.apache.org/jira/browse/SYNCOPE-323
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.5, 1.1.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
>
> I have recently found that some REST create requests are treated as update.
> For example, try to create a new schema on the admin console and provide a 
> name of another existing schema: you won't get any warning; only, the 
> existing schema definition will be completely replaced by the newly inserted 
> entry.
> After some investigations, I've found that this happens for external 
> resources, schema, derived schema and virtual schema.
> Such entities have in common the fact that the JPA @Id is non-generated.
> The way how saving is handled (via EntityManager#merge()) finally turns an 
> expected create into an update.
> I don't find such behavior as correct, hence I would propose to throw an 
> exception, in the REST create methods for the entities named above, in case 
> the key of the entity being created is already present. 
> [1] http://markmail.org/message/kxrh7pgwuijwyfik

--
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] REST: create turns into update for some entities

[Francesco Chicchiriccò]

On 22/02/2013 16:13, Andrei Shakirin wrote:

Hi Francesco,

+1 for issue.
Find it also quite dangerous, create() should throw exception if entity already exists, 
"409 Conflict" will be corresponded HTTP error code in this case.


Done, thanks for the tip ;-)

Have a nice WE.


-Original Message-
From: Francesco Chicchiriccò [mailto:ilgro...@apache.org]
Sent: Freitag, 22. Februar 2013 14:44
To: dev@syncope.apache.org
Subject: Re: [DISCUSS] REST: create turns into update for some entities

I have opened SYNCOPE-323 for this.

Regards.

On 22/02/2013 12:43, Francesco Chicchiriccò wrote:

Hi all,
I have recently found that some REST create requests are treated as
update.

For example, try to create a new schema on the admin console and
provide a name of another existing schema: you won't get any warning;
only, the existing schema definition will be completely replaced by
the newly inserted entry.

After some investigations, I've found that this happens for external
resources, schema, derived schema and virtual schema.
Such entities have in common the fact that the JPA @Id is non-generated.
The way how saving is handled (via EntityManager#merge()) finally
turns an expected create into an update.

I don't find such behavior as correct, hence I would propose to throw
an exception, in the REST create methods for the entities named above,
in case the key of the entity being created is already present.

Do you see any problem with this?


--
Francesco Chicchiriccò

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

[jira] [Updated] (SYNCOPE-309) Enter key not bound to user form submit

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-309:
---

Fix Version/s: 1.0.6

> Enter key not bound to user form submit
> ---
>
> Key: SYNCOPE-309
> URL: https://issues.apache.org/jira/browse/SYNCOPE-309
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 1.0.5, 1.1.0
> Environment: Google Chrome
>Reporter: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 1.0.6, 1.1.0
>
>
> When editing an user from the admin console, if entering an attribute value 
> and hitting 'enter', a derived attribute is added.
> Since this happens in another tab, when clicking on Save to submit the form, 
> an error is reported "'Schema' is required".

--
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-309) Enter key not bound to user form submit

[JIRA]

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

Francesco Chicchiriccò updated SYNCOPE-309:
---

Affects Version/s: 1.0.5

> Enter key not bound to user form submit
> ---
>
> Key: SYNCOPE-309
> URL: https://issues.apache.org/jira/browse/SYNCOPE-309
> Project: Syncope
>  Issue Type: Bug
>  Components: console
>Affects Versions: 1.0.5, 1.1.0
> Environment: Google Chrome
>Reporter: Francesco Chicchiriccò
>Priority: Minor
> Fix For: 1.1.0
>
>
> When editing an user from the admin console, if entering an attribute value 
> and hitting 'enter', a derived attribute is added.
> Since this happens in another tab, when clicking on Save to submit the form, 
> an error is reported "'Schema' is required".

--
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 # 108 - Fixed

[Apache Jenkins Server]

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

Status: Fixed

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

[jira] [Commented] (SYNCOPE-323) REST: create turns into update for some entities

[Hudson (JIRA)]

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

Hudson commented on SYNCOPE-323:


Integrated in Syncope-trunk #108 (See 
[https://builds.apache.org/job/Syncope-trunk/108/])
[SYNCOPE-323] Check added in the REST create methods, throwing exception 
mapped to HTTP 409 CONFLICT as suggested (Revision 1449107)

 Result = SUCCESS
ilgrosso : 
Files : 
* 
/syncope/trunk/client/src/main/java/org/apache/syncope/client/rest/utils/RestClientExceptionMapper.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientCompositeErrorException.java
* 
/syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientErrorHandler.java
* 
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/SchemaModalPage.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ConnInstanceController.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/DerivedSchemaController.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ResourceController.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/SchemaController.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/VirtualSchemaController.java
* 
/syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/utils/RestServiceExceptionMapper.java
* /syncope/trunk/core/src/main/webapp/syncopeClientError.jsp
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/DerivedSchemaTestITCase.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ResourceTestITCase.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/SchemaTestITCase.java
* 
/syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/VirtualSchemaTestITCase.java


> REST: create turns into update for some entities
> 
>
> Key: SYNCOPE-323
> URL: https://issues.apache.org/jira/browse/SYNCOPE-323
> Project: Syncope
>  Issue Type: Bug
>  Components: core
>Affects Versions: 1.0.5, 1.1.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.1.0
>
>
> I have recently found that some REST create requests are treated as update.
> For example, try to create a new schema on the admin console and provide a 
> name of another existing schema: you won't get any warning; only, the 
> existing schema definition will be completely replaced by the newly inserted 
> entry.
> After some investigations, I've found that this happens for external 
> resources, schema, derived schema and virtual schema.
> Such entities have in common the fact that the JPA @Id is non-generated.
> The way how saving is handled (via EntityManager#merge()) finally turns an 
> expected create into an update.
> I don't find such behavior as correct, hence I would propose to throw an 
> exception, in the REST create methods for the entities named above, in case 
> the key of the entity being created is already present. 
> [1] http://markmail.org/message/kxrh7pgwuijwyfik

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