[jira] [Updated] (SYNCOPE-514) Core doesn't deploy on Glassfish
[ https://issues.apache.org/jira/browse/SYNCOPE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone updated SYNCOPE-514: - Description: Now, trying to deploy the core on Glassfish 4 the result is: [17:07:50.688][info][talledLocalContainer] remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in file [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError: org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;. Please see server.log for more details. I have been able to deploy it deleting bval dependencies and replacing them with hibernate-validator libraries. Considering that SYNCOPE-461 suggests to replace BVal with Hibernate Validator, what do you think to replace it now? was: Now, trying to deploy the core on Glassfish 4 the result is: [17:07:50.688][info][talledLocalContainer] remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in file [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError: org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;. Please see server.log for more details. I have been able to deploy it deleting bval dependencies and replacing them with hibernate-validator libraries. Considering that SYNCOPE-46 suggests to replace BVal with Hibernate Validator, what do you think to replace it now? Core doesn't deploy on Glassfish Key: SYNCOPE-514 URL: https://issues.apache.org/jira/browse/SYNCOPE-514 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Environment: Glassfish 4 Reporter: Massimiliano Perrone Assignee: Massimiliano Perrone Fix For: 1.2.0 Now, trying to deploy the core on Glassfish 4 the result is: [17:07:50.688][info][talledLocalContainer] remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in file [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError: org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;. Please see server.log for more details. I have been able to deploy it deleting bval dependencies and replacing them with hibernate-validator libraries. Considering that SYNCOPE-461 suggests to replace BVal with Hibernate Validator, what do you think to replace it now? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-461) Use BeanValidation 1.1 with JAX-RS services
[ https://issues.apache.org/jira/browse/SYNCOPE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041823#comment-14041823 ] ASF subversion and git services commented on SYNCOPE-461: - Commit 1605022 from [~massi] in branch 'syncope/trunk' [ https://svn.apache.org/r1605022 ] BVal libraries replaced with Hibernate Validatorin #SYNCOPE-461 Use BeanValidation 1.1 with JAX-RS services --- Key: SYNCOPE-461 URL: https://issues.apache.org/jira/browse/SYNCOPE-461 Project: Syncope Issue Type: Improvement Components: common, core Reporter: Francesco Chicchiriccò Labels: rest Fix For: 1.2.0 CXF supports JAX-RS bean validation 1.1 [1]. Unfortunately, the available implementations are either Hibernate Validator or Apache BVal 1.0, not yet released (1.0-alpha-SNAPSHOT available). Syncope already features BVal 0.5 for OpenJPA bean validation, so the logical choice is to wait for BVal 1.0 to be generally available. [1] http://cxf.apache.org/docs/validationfeature.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-514) Core doesn't deploy on Glassfish
[ https://issues.apache.org/jira/browse/SYNCOPE-514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041829#comment-14041829 ] Massimiliano Perrone commented on SYNCOPE-514: -- Commit 1605022 from Massimiliano Perrone in branch 'syncope/trunk' [ https://svn.apache.org/r1605022 ] BVal libraries replaced with Hibernate Validatorin #SYNCOPE-461 PS: glassfish-it maven profile does not build. Core doesn't deploy on Glassfish Key: SYNCOPE-514 URL: https://issues.apache.org/jira/browse/SYNCOPE-514 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Environment: Glassfish 4 Reporter: Massimiliano Perrone Assignee: Massimiliano Perrone Fix For: 1.2.0 Now, trying to deploy the core on Glassfish 4 the result is: [17:07:50.688][info][talledLocalContainer] remote failure: Error occurred during deployment: Exception while loading the app : java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'validator' defined in file [/tmp/trunk/core/target/syncope-core-test/WEB-INF/classes/persistenceContext.xml]: Invocation of init method failed; nested exception is java.lang.AbstractMethodError: org.apache.bval.jsr303.ConfigurationImpl.getDefaultParameterNameProvider()Ljavax/validation/ParameterNameProvider;. Please see server.log for more details. I have been able to deploy it deleting bval dependencies and replacing them with hibernate-validator libraries. Considering that SYNCOPE-461 suggests to replace BVal with Hibernate Validator, what do you think to replace it now? -- This message was sent by Atlassian JIRA (v6.2#6252)
R: [Proposal] Syncope LDAP Interface
Hi In general I'm proposing a read/write LDAP interface ahead Syncope. The real needing is to perfoms LDAP operations against Syncope. It happens when the applications need to connect to an authoritative resource, via LDAP. Very often the requested feature is the password sync, so the user that change his password using a web application (like an intranet) obtains to propagate the password change (by Syncope) to all his resources. Or in other cases is easy performing users bulk actions using a simple add/replace ldif, without writing extra code. Regards, Mirko Signoretto -Messaggio originale- Da: Emmanuel Lécharny [mailto:elecha...@gmail.com] Inviato: mercoledì 18 giugno 2014 10:06 A: dev@syncope.apache.org Oggetto: Re: [Proposal] Syncope LDAP Interface Le 17/06/2014 15:31, Francesco Chicchiriccò a écrit : Hi, generally speaking, you are proposing to provide Syncope with a (read-only) LDAP interface for users and roles, suitable for enhancing Syncope's integration capabilities. ATM the simpler way to achieve this is to configure a bundled ApacheDS instance that will be assigned to all users and roles. Did you had a look at Fortress (http://www.openldap.org/fortress/) ?
[jira] [Commented] (SYNCOPE-505) Support propagating non-cleartext passwords to external resources
[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041884#comment-14041884
]
Francesco Chicchiriccò commented on SYNCOPE-505:
[~coheigea], I've taken a look at {{LDAPPropagationActions}} and it looks good,
nice job!
Now, as you suggest, we need to open an issue on the LDAP connector for not
hashing password values when on the form
{code}
{HASH}value
{code}
with {{HASH}} different from {{CLEARTEXT}}: it shouldn't be an hard
modification, actually.
Support propagating non-cleartext passwords to external resources
-
Key: SYNCOPE-505
URL: https://issues.apache.org/jira/browse/SYNCOPE-505
Project: Syncope
Issue Type: Improvement
Components: core
Reporter: Francesco Chicchiriccò
Assignee: Colm O hEigeartaigh
Fix For: 1.2.0
Similarly to SYNCOPE-313 during synchronization, it seems feasible to provide
some Propagation Actions classes (say {{DBPasswordPropagationActions}} and
{{LDAPPasswordPropagationActions}} that will propagate non-cleartext password
values to external resources.
This might require some changes in the related connector bundles.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (SYNCOPE-505) Support propagating non-cleartext passwords to external resources
[
https://issues.apache.org/jira/browse/SYNCOPE-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041899#comment-14041899
]
Francesco Chicchiriccò commented on SYNCOPE-505:
Here you go: https://connid.atlassian.net/browse/LDAP-13
Support propagating non-cleartext passwords to external resources
-
Key: SYNCOPE-505
URL: https://issues.apache.org/jira/browse/SYNCOPE-505
Project: Syncope
Issue Type: Improvement
Components: core
Reporter: Francesco Chicchiriccò
Assignee: Colm O hEigeartaigh
Fix For: 1.2.0
Similarly to SYNCOPE-313 during synchronization, it seems feasible to provide
some Propagation Actions classes (say {{DBPasswordPropagationActions}} and
{{LDAPPasswordPropagationActions}} that will propagate non-cleartext password
values to external resources.
This might require some changes in the related connector bundles.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
Task Rules
Hi all, What are the new task rules that have been added to trunk? When I create a new synchronization task with the default Matching/Update Unmatching/Assign, it appears that the selected LDAPPasswordSyncActions class is not run. Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: Task Rules
Il 24/06/2014 12:24, Colm O hEigeartaigh ha scritto: Hi all, What are the new task rules that have been added to trunk? When I create a new synchronization task with the default Matching/Update Unmatching/Assign, it appears that the selected LDAPPasswordSyncActions class is not run. Colm. Hi Colm, matching/unmatching rules can be configured in order to specify a specific behaviour in case of matching (sync user found locally) and unmatching (sync user not found locally) scenarios. For example, I can ask to syncope to unlink the synchronized resource from the local account that matches the synchronized one. This is the issue [1], still in progress: maybe you are facing with a bug (maybe just on the admin console). If you can/want, please investigate more, otherwise, be patient: we will fix it very soon. Best regards, F. [1] https://issues.apache.org/jira/browse/SYNCOPE-471 -- Fabio Martelli Tirasa - Open Source Excellence http://www.tirasa.net/ Apache Syncope PMC http://people.apache.org/~fmartelli/
[jira] [Created] (SYNCOPE-515) Bad integration test causes role ownership conflicts
fabio martelli created SYNCOPE-515: -- Summary: Bad integration test causes role ownership conflicts Key: SYNCOPE-515 URL: https://issues.apache.org/jira/browse/SYNCOPE-515 Project: Syncope Issue Type: Bug Affects Versions: 1.1.7, 1.2.0 Reporter: fabio martelli Fix For: 1.1.8, 1.2.0 Reproduce with mvn clean verify -Dit.test=*e*TestITCase -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-515) Bad integration test causes role ownership conflicts
[ https://issues.apache.org/jira/browse/SYNCOPE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli reassigned SYNCOPE-515: -- Assignee: fabio martelli Bad integration test causes role ownership conflicts Key: SYNCOPE-515 URL: https://issues.apache.org/jira/browse/SYNCOPE-515 Project: Syncope Issue Type: Bug Affects Versions: 1.1.7, 1.2.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.8, 1.2.0 Reproduce with mvn clean verify -Dit.test=*e*TestITCase -- This message was sent by Atlassian JIRA (v6.2#6252)
Binary Schema UI enhancements
Hi all, I've had a change to look at the changes made as part of SYNCOPE-123, to support binary attributes. I can now load a X509 Certificate + associate it with a user, and propagate (+ sync) it to LDAP via the userCertificate attribute. Nice work Francesco! I just have some minor UI enhancement ideas: a) Instead of making the user input a MIME Type, why not just have a dropdown list with (e.g.) the following? http://www.sitepoint.com/web-foundations/mime-types-complete-list/ b) I think the User UI needs some work. Right now, there is no way of telling whether a user has an associated binary attribute by looking at the screen, you need to download the attribute and see if it has content or not. Maybe we could have a checkbox that shows whether the attribute has content or not? Or we could display the total byte count of the attribute or something? Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
[jira] [Commented] (SYNCOPE-515) Bad integration test causes role ownership conflicts
[ https://issues.apache.org/jira/browse/SYNCOPE-515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042088#comment-14042088 ] ASF subversion and git services commented on SYNCOPE-515: - Commit 1605076 from [~fmartelli] in branch 'syncope/branches/1_1_X' [ https://svn.apache.org/r1605076 ] [SYNCOPE-515] fix for the branch Bad integration test causes role ownership conflicts Key: SYNCOPE-515 URL: https://issues.apache.org/jira/browse/SYNCOPE-515 Project: Syncope Issue Type: Bug Affects Versions: 1.1.7, 1.2.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.8, 1.2.0 Reproduce with mvn clean verify -Dit.test=*e*TestITCase -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-290) Typed SyncopeConf
[ https://issues.apache.org/jira/browse/SYNCOPE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042095#comment-14042095 ] ASF subversion and git services commented on SYNCOPE-290: - Commit 1605077 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1605077 ] [SYNCOPE-290] Implementation completed Typed SyncopeConf - Key: SYNCOPE-290 URL: https://issues.apache.org/jira/browse/SYNCOPE-290 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.2.0 Attachments: SYNCOPE-290.png Currently SyncopeConf instances are String, String pairs: this has of course various drawbacks (no check for mandatory values, enums not available, ...) It should be relatively easy to create a set of SSchema / SAttr / SAttrValue / SAttrUniqueValue (similar to what currently available for user / membership / role) to replace the current SyncopeConf. -- This message was sent by Atlassian JIRA (v6.2#6252)
Running Syncope Embed using a permanent h2 instance
Hi, I've checked out Syncope 1_1_X to do some tests. I've seen that Syncope h2 db it's created within target directory. Everytime I launch mvn -P debug, target dir it's deleted. I'm wondering if is there a way to launch Syncope embed mode/debug profile using a permanent h2 location. I've tried adding a customized persistence.properties file in syncope-console\src\resources specifying both absolute and relative path outside target dir but it seems workdir it's needed. Is there a better way to do it or get the same result ? Best regards Thanks, Denis.
Re: Binary Schema UI enhancements
On 24/06/2014 15:18, Colm O hEigeartaigh wrote: Hi all, I've had a change to look at the changes made as part of SYNCOPE-123, to support binary attributes. I can now load a X509 Certificate + associate it with a user, and propagate (+ sync) it to LDAP via the userCertificate attribute. Nice work Francesco! Thanks Colm :-) I just have some minor UI enhancement ideas: a) Instead of making the user input a MIME Type, why not just have a dropdown list with (e.g.) the following? http://www.sitepoint.com/web-foundations/mime-types-complete-list/ Why don't we put instead an auto-complete field featuring this list - can't believe CXF hasn't turned it yet into a handful constant class ;-) - instead? Being the list very long, a plain dropdown would be less handy, IMO, and would also prohibit any non-standard input (say a mimeType only valid within a company or so). b) I think the User UI needs some work. Right now, there is no way of telling whether a user has an associated binary attribute by looking at the screen, you need to download the attribute and see if it has content or not. Maybe we could have a checkbox that shows whether the attribute has content or not? Or we could display the total byte count of the attribute or something? You are right. Since AFAIK Andrea is currently thinking about how to provide a pluggable binary viewer mechanism (as we discussed in [1]), we could open an issue for Binary Schema UI enhancements and include the notes above + [1]. WDYT? [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/
[jira] [Resolved] (SYNCOPE-290) Typed SyncopeConf
[ https://issues.apache.org/jira/browse/SYNCOPE-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò resolved SYNCOPE-290. Resolution: Fixed Typed SyncopeConf - Key: SYNCOPE-290 URL: https://issues.apache.org/jira/browse/SYNCOPE-290 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.2.0 Attachments: SYNCOPE-290.png Currently SyncopeConf instances are String, String pairs: this has of course various drawbacks (no check for mandatory values, enums not available, ...) It should be relatively easy to create a set of SSchema / SAttr / SAttrValue / SAttrUniqueValue (similar to what currently available for user / membership / role) to replace the current SyncopeConf. -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Running Syncope Embed using a permanent h2 instance
On 24/06/2014 15:27, Denis Signoretto wrote: Hi, I've checked out Syncope 1_1_X to do some tests. I've seen that Syncope h2 db it's created within target directory. Everytime I launch mvn -P debug, target dir it's deleted. This means you are directly running from the actual Syncope sources: I'd suggest you instead to generate your own project from SNAPSHOT archetype [1] and then run in embedded mode [2] via mvn -P embedded. I'm wondering if is there a way to launch Syncope embed mode/debug profile using a permanent h2 location. I've tried adding a customized persistence.properties file in syncope-console\src\resources specifying both absolute and relative path outside target dir but it seems workdir it's needed. Is there a better way to do it or get the same result ? You can proceed similar to the standalone distribution [3]: only, you need to change core/src/test/resources/persistence.properties not core/src/main/resources/persistence.properties The former is used for tests and for embedded mode, the latter for production, e.g. for the WAR to be deployed into a real-world deployment. HTH Regards. [1] https://cwiki.apache.org/confluence/display/SYNCOPE/Create+a+new+Syncope+project#CreateanewSyncopeproject-Snapshot(development)releases [2] https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+in+embedded+mode [3] https://cwiki.apache.org/confluence/display/SYNCOPE/Run+Syncope+standalone+distribution#RunSyncopestandalonedistribution-Internalstorage -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/
Re: Binary Schema UI enhancements
Hi Francesco, On Tue, Jun 24, 2014 at 2:28 PM, Francesco Chicchiriccò ilgro...@apache.org wrote: Why don't we put instead an auto-complete field featuring this list - can't believe CXF hasn't turned it yet into a handful constant class ;-) - instead? Being the list very long, a plain dropdown would be less handy, IMO, and would also prohibit any non-standard input (say a mimeType only valid within a company or so). +1 sounds good. Since AFAIK Andrea is currently thinking about how to provide a pluggable binary viewer mechanism (as we discussed in [1]), we could open an issue for Binary Schema UI enhancements and include the notes above + [1]. WDYT? [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html +1 as well. Would this be done for 1.2? Colm.
[jira] [Assigned] (SYNCOPE-461) Use BeanValidation 1.1 with JAX-RS services
[ https://issues.apache.org/jira/browse/SYNCOPE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò reassigned SYNCOPE-461: -- Assignee: Francesco Chicchiriccò Use BeanValidation 1.1 with JAX-RS services --- Key: SYNCOPE-461 URL: https://issues.apache.org/jira/browse/SYNCOPE-461 Project: Syncope Issue Type: Improvement Components: common, core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Labels: rest Fix For: 1.2.0 CXF supports JAX-RS bean validation 1.1 [1]. Unfortunately, the available implementations are either Hibernate Validator or Apache BVal 1.0, not yet released (1.0-alpha-SNAPSHOT available). Syncope already features BVal 0.5 for OpenJPA bean validation, so the logical choice is to wait for BVal 1.0 to be generally available. [1] http://cxf.apache.org/docs/validationfeature.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-516) Binary Schema UI enhancements
Andrea Patricelli created SYNCOPE-516: - Summary: Binary Schema UI enhancements Key: SYNCOPE-516 URL: https://issues.apache.org/jira/browse/SYNCOPE-516 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display total byte count of the attribute in User UI. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- This message was sent by Atlassian JIRA (v6.2#6252)
Re: Binary Schema UI enhancements
Hi Colm, On 24/06/2014 15:36, Colm O hEigeartaigh wrote: Hi Francesco, On Tue, Jun 24, 2014 at 2:28 PM, Francesco Chicchiriccò ilgro...@apache.org wrote: Why don't we put instead an auto-complete field featuring this list - can't believe CXF hasn't turned it yet into a handful constant class ;-) - instead? Being the list very long, a plain dropdown would be less handy, IMO, and would also prohibit any non-standard input (say a mimeType only valid within a company or so). +1 sounds good. Since AFAIK Andrea is currently thinking about how to provide a pluggable binary viewer mechanism (as we discussed in [1]), we could open an issue for Binary Schema UI enhancements and include the notes above + [1]. WDYT? [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html +1 as well. Would this be done for 1.2? Yes, I just opened [1]. [1] https://issues.apache.org/jira/browse/SYNCOPE-516 Colm. Regards, Andrea -- Dott. Andrea Patricelli Tel +393204524292 Junior Engineer @ Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +390859116307 / FAX +39 085973 http://www.tirasa.net
[jira] [Commented] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042136#comment-14042136 ] Colm O hEigeartaigh commented on SYNCOPE-516: - The byte count is probably not necessary IMO, if the third point allows for a simple way to see whether an attribute has a value or not. Colm. Binary Schema UI enhancements - Key: SYNCOPE-516 URL: https://issues.apache.org/jira/browse/SYNCOPE-516 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display total byte count of the attribute in User UI. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042159#comment-14042159 ] Andrea Patricelli commented on SYNCOPE-516: --- You are right, reading file size in edit mode would probably be inefficient. But since there are two arrows (upload/download) next to the attribute, we could, first of all, think to disable download link if attribute is not populated and so different opacity of download arrow can show us if there's some uploaded file or not (or even arrow could not be shown at all), WDYT? Binary Schema UI enhancements - Key: SYNCOPE-516 URL: https://issues.apache.org/jira/browse/SYNCOPE-516 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display total byte count of the attribute in User UI. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-461) Use BeanValidation 1.1 with JAX-RS services
[ https://issues.apache.org/jira/browse/SYNCOPE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042165#comment-14042165 ] ASF subversion and git services commented on SYNCOPE-461: - Commit 1605090 from [~ilgrosso] in branch 'syncope/trunk' [ https://svn.apache.org/r1605090 ] [SYNCOPE-461] Preliminary commit: removing deprecated methods and setting deps as indicated by CXF Use BeanValidation 1.1 with JAX-RS services --- Key: SYNCOPE-461 URL: https://issues.apache.org/jira/browse/SYNCOPE-461 Project: Syncope Issue Type: Improvement Components: common, core Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Labels: rest Fix For: 1.2.0 CXF supports JAX-RS bean validation 1.1 [1]. Unfortunately, the available implementations are either Hibernate Validator or Apache BVal 1.0, not yet released (1.0-alpha-SNAPSHOT available). Syncope already features BVal 0.5 for OpenJPA bean validation, so the logical choice is to wait for BVal 1.0 to be generally available. [1] http://cxf.apache.org/docs/validationfeature.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042209#comment-14042209 ] Colm O hEigeartaigh commented on SYNCOPE-516: - Yes that makes sense I think! Colm. Binary Schema UI enhancements - Key: SYNCOPE-516 URL: https://issues.apache.org/jira/browse/SYNCOPE-516 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display total byte count of the attribute in User UI. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-516: -- Description: Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display whether attribute has value or not, working on download arrow opacity. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html was: Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display total byte count of the attribute in User UI. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html Binary Schema UI enhancements - Key: SYNCOPE-516 URL: https://issues.apache.org/jira/browse/SYNCOPE-516 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display whether attribute has value or not, working on download arrow opacity. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042214#comment-14042214 ] Andrea Patricelli commented on SYNCOPE-516: --- Good, I'll update the issue. Binary Schema UI enhancements - Key: SYNCOPE-516 URL: https://issues.apache.org/jira/browse/SYNCOPE-516 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display whether attribute has value or not, working on download arrow opacity. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- This message was sent by Atlassian JIRA (v6.2#6252)
Errored: apache/syncope#617 (trunk - 9b07243)
Build Update for apache/syncope - Build: #617 Status: Errored Duration: 1 minute and 27 seconds Commit: 9b07243 (trunk) Author: Francesco Chicchiriccò Message: [SYNCOPE-290] Implementation completed git-svn-id: https://svn.apache.org/repos/asf/syncope/trunk@1605077 13f79535-47bb-0310-9956-ffa450edef68 View the changeset: https://github.com/apache/syncope/compare/a33879c1495a...9b0724340e7a View the full build log and details: https://travis-ci.org/apache/syncope/builds/28316422 -- You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications
