[jira] [Assigned] (SYNCOPE-498) Connector SpinnerFieldPanel required values
[ https://issues.apache.org/jira/browse/SYNCOPE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-498: -- Assignee: Francesco Chicchiriccò > Connector SpinnerFieldPanel required values > --- > > Key: SYNCOPE-498 > URL: https://issues.apache.org/jira/browse/SYNCOPE-498 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: Colm O hEigeartaigh >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 1.2.0 > > > With the latest Syncope trunk code, I noticed that if I create a new LDAP > Connector (1.3.6) it appears to be requiring me to enter a Block Size + > Change Log Block Size, even though these parameters are optional and both > default to 100. You can reproduce by just creating an LDAP Connector + > clicking on save. At the top of the screen you can see: >'Host' is required. > 'TCP Port' is required. > 'Base Contexts' is required. > 'Block Size' is required. > 'Change Log Block Size' is required. > The issue seems to be related to the new component "SpinnerFieldPanel" used > to represents numeric connector configuration properties. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-479) Use X-Application-Error-Code Response header instead of ExceptionType
[ https://issues.apache.org/jira/browse/SYNCOPE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-479. Resolution: Fixed > Use X-Application-Error-Code Response header instead of ExceptionType > - > > Key: SYNCOPE-479 > URL: https://issues.apache.org/jira/browse/SYNCOPE-479 > Project: Syncope > Issue Type: Improvement > Components: client, core >Affects Versions: 1.2.0 >Reporter: Oliver Wulff >Assignee: Francesco Chicchiriccò > Labels: rest > Fix For: 1.2.0 > > > The REST service return more detailed exception information beyond the HTTP > error code in the HTTP header 'ExceptionType' and some other HTTP Resonse > header. > Due to some other sources in the web, the best practise approach is to use > the HTTP Response headers: > X-Application-Error-Code and X-Application-Error-Info > See discussion here: > http://mail-archives.apache.org/mod_mbox/syncope-dev/201401.mbox/%3C52E61B5D.6080201%40apache.org%3E -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-479) Use X-Application-Error-Code Response header instead of ExceptionType
[ https://issues.apache.org/jira/browse/SYNCOPE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013596#comment-14013596 ] ASF subversion and git services commented on SYNCOPE-479: - Commit 1598567 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1598567 ] [SYNCOPE-479] Now using X-Application-Error-Code and X-Application-Error-Info header names for error reporting - more REST best practices > Use X-Application-Error-Code Response header instead of ExceptionType > - > > Key: SYNCOPE-479 > URL: https://issues.apache.org/jira/browse/SYNCOPE-479 > Project: Syncope > Issue Type: Improvement > Components: client, core >Affects Versions: 1.2.0 >Reporter: Oliver Wulff >Assignee: Francesco Chicchiriccò > Labels: rest > Fix For: 1.2.0 > > > The REST service return more detailed exception information beyond the HTTP > error code in the HTTP header 'ExceptionType' and some other HTTP Resonse > header. > Due to some other sources in the web, the best practise approach is to use > the HTTP Response headers: > X-Application-Error-Code and X-Application-Error-Info > See discussion here: > http://mail-archives.apache.org/mod_mbox/syncope-dev/201401.mbox/%3C52E61B5D.6080201%40apache.org%3E -- This message was sent by Atlassian JIRA (v6.2#6252)
Errored: apache/syncope#557 (trunk - 2ff06cd)
Build Update for apache/syncope - Build: #557 Status: Errored Duration: 11 minutes and 41 seconds Commit: 2ff06cd (trunk) Author: Colm O Heigeartaigh Message: Minor cleanup git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1598550 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/b77276f83c1b...2ff06cd46307 View the full build log and details: https://travis-ci.org/apache/syncope/builds/26375621 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
Re: Required values with LDAP Connector on trunk
Yup, here it is: https://issues.apache.org/jira/browse/SYNCOPE-498 Colm. On Fri, May 30, 2014 at 11:44 AM, Fabio Martelli wrote: > Il 29/05/2014 17:47, Colm O hEigeartaigh ha scritto: > > Hi all, >> >> With the latest Syncope trunk code, I noticed that if I create a new LDAP >> Connector (1.3.6) it appears to be requiring me to enter a Block Size + >> Change Log Block Size, even though these parameters are optional and both >> default to 100. You can reproduce by just creating an LDAP Connector + >> clicking on save. At the top of the screen you can see: >> >> 'Host' is required. >> 'TCP Port' is required. >> 'Base Contexts' is required. >> 'Block Size' is required. >> 'Change Log Block Size' is required. >> >> Is anyone aware of any changes here? I'm pretty sure I tested with ConnId >> LDAP 1.3.6 before and Syncope + it worked without these values. >> >> Colm. >> > Hi Colm, you are right, Block Size and Change Log Block Size shouldn't be > mandatory. > The issue seems to be related to the new component "SpinnerFieldPanel" > used to represents numeric connector configuration properties. > > Can I ask you to open a new issue? > > Best regards, > F. > > -- > Fabio Martelli > > Tirasa - Open Source Excellence > http://www.tirasa.net/ > > Apache Syncope PMC > http://people.apache.org/~fmartelli/ > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
[jira] [Created] (SYNCOPE-498) Connector SpinnerFieldPanel required values
Colm O hEigeartaigh created SYNCOPE-498: --- Summary: Connector SpinnerFieldPanel required values Key: SYNCOPE-498 URL: https://issues.apache.org/jira/browse/SYNCOPE-498 Project: Syncope Issue Type: Bug Components: console Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 1.2.0 With the latest Syncope trunk code, I noticed that if I create a new LDAP Connector (1.3.6) it appears to be requiring me to enter a Block Size + Change Log Block Size, even though these parameters are optional and both default to 100. You can reproduce by just creating an LDAP Connector + clicking on save. At the top of the screen you can see: 'Host' is required. 'TCP Port' is required. 'Base Contexts' is required. 'Block Size' is required. 'Change Log Block Size' is required. The issue seems to be related to the new component "SpinnerFieldPanel" used to represents numeric connector configuration properties. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Required values with LDAP Connector on trunk
Il 29/05/2014 17:47, Colm O hEigeartaigh ha scritto: Hi all, With the latest Syncope trunk code, I noticed that if I create a new LDAP Connector (1.3.6) it appears to be requiring me to enter a Block Size + Change Log Block Size, even though these parameters are optional and both default to 100. You can reproduce by just creating an LDAP Connector + clicking on save. At the top of the screen you can see: 'Host' is required. 'TCP Port' is required. 'Base Contexts' is required. 'Block Size' is required. 'Change Log Block Size' is required. Is anyone aware of any changes here? I'm pretty sure I tested with ConnId LDAP 1.3.6 before and Syncope + it worked without these values. Colm. Hi Colm, you are right, Block Size and Change Log Block Size shouldn't be mandatory. The issue seems to be related to the new component "SpinnerFieldPanel" used to represents numeric connector configuration properties. Can I ask you to open a new issue? Best regards, F. -- Fabio Martelli Tirasa - Open Source Excellence http://www.tirasa.net/ Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Assigned] (SYNCOPE-479) Use X-Application-Error-Code Response header instead of ExceptionType
[ https://issues.apache.org/jira/browse/SYNCOPE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-479: -- Assignee: Francesco Chicchiriccò > Use X-Application-Error-Code Response header instead of ExceptionType > - > > Key: SYNCOPE-479 > URL: https://issues.apache.org/jira/browse/SYNCOPE-479 > Project: Syncope > Issue Type: Improvement > Components: client, core >Affects Versions: 1.2.0 >Reporter: Oliver Wulff >Assignee: Francesco Chicchiriccò > Labels: rest > Fix For: 1.2.0 > > > The REST service return more detailed exception information beyond the HTTP > error code in the HTTP header 'ExceptionType' and some other HTTP Resonse > header. > Due to some other sources in the web, the best practise approach is to use > the HTTP Response headers: > X-Application-Error-Code and X-Application-Error-Info > See discussion here: > http://mail-archives.apache.org/mod_mbox/syncope-dev/201401.mbox/%3C52E61B5D.6080201%40apache.org%3E -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-497) JEXL Frame positioning error
[ https://issues.apache.org/jira/browse/SYNCOPE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013492#comment-14013492 ] Francesco Chicchiriccò commented on SYNCOPE-497: Not sure this is possible, given the fact that "modal windows" are just iframes: probably the only thing we can do is to set the wider initial dimensions for that modal window... > JEXL Frame positioning error > > > Key: SYNCOPE-497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-497 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.2.0 > > Attachments: jexl-error.png > > > There is a problem with a JEXL frame positioning on trunk, where the help > message does not appear properly on the screen (see attached png). > Steps to reproduce: > Tasks -> Synchronization Task -> Create User template > Click on the "help" for "Username". The result is the attached on both > firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-497) JEXL Frame positioning error
[ https://issues.apache.org/jira/browse/SYNCOPE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013491#comment-14013491 ] Colm O hEigeartaigh commented on SYNCOPE-497: - Well it's quite trivial :-) However the message should appear without the user having to scroll to read it. Colm. > JEXL Frame positioning error > > > Key: SYNCOPE-497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-497 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.2.0 > > Attachments: jexl-error.png > > > There is a problem with a JEXL frame positioning on trunk, where the help > message does not appear properly on the screen (see attached png). > Steps to reproduce: > Tasks -> Synchronization Task -> Create User template > Click on the "help" for "Username". The result is the attached on both > firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-497) JEXL Frame positioning error
[ https://issues.apache.org/jira/browse/SYNCOPE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013490#comment-14013490 ] Francesco Chicchiriccò commented on SYNCOPE-497: Is this a real error or barely the fact that the modal window is too small and needs to be enlarged? > JEXL Frame positioning error > > > Key: SYNCOPE-497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-497 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.2.0 > > Attachments: jexl-error.png > > > There is a problem with a JEXL frame positioning on trunk, where the help > message does not appear properly on the screen (see attached png). > Steps to reproduce: > Tasks -> Synchronization Task -> Create User template > Click on the "help" for "Username". The result is the attached on both > firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-497) JEXL Frame positioning error
[ https://issues.apache.org/jira/browse/SYNCOPE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-497: --- Component/s: console > JEXL Frame positioning error > > > Key: SYNCOPE-497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-497 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.2.0 > > Attachments: jexl-error.png > > > There is a problem with a JEXL frame positioning on trunk, where the help > message does not appear properly on the screen (see attached png). > Steps to reproduce: > Tasks -> Synchronization Task -> Create User template > Click on the "help" for "Username". The result is the attached on both > firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-497) JEXL Frame positioning error
[ https://issues.apache.org/jira/browse/SYNCOPE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colm O hEigeartaigh updated SYNCOPE-497: Attachment: jexl-error.png > JEXL Frame positioning error > > > Key: SYNCOPE-497 > URL: https://issues.apache.org/jira/browse/SYNCOPE-497 > Project: Syncope > Issue Type: Bug >Reporter: Colm O hEigeartaigh >Priority: Minor > Fix For: 1.2.0 > > Attachments: jexl-error.png > > > There is a problem with a JEXL frame positioning on trunk, where the help > message does not appear properly on the screen (see attached png). > Steps to reproduce: > Tasks -> Synchronization Task -> Create User template > Click on the "help" for "Username". The result is the attached on both > firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-497) JEXL Frame positioning error
Colm O hEigeartaigh created SYNCOPE-497: --- Summary: JEXL Frame positioning error Key: SYNCOPE-497 URL: https://issues.apache.org/jira/browse/SYNCOPE-497 Project: Syncope Issue Type: Bug Reporter: Colm O hEigeartaigh Priority: Minor Fix For: 1.2.0 Attachments: jexl-error.png There is a problem with a JEXL frame positioning on trunk, where the help message does not appear properly on the screen (see attached png). Steps to reproduce: Tasks -> Synchronization Task -> Create User template Click on the "help" for "Username". The result is the attached on both firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
