[
https://issues.apache.org/jira/browse/SYNCOPE-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420353#comment-16420353
]
ASF subversion and git services commented on SYNCOPE-956:
---------------------------------------------------------
Commit 80083118c9bdd9f2e45803de16a5e21174474a9d in syncope's branch
refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=8008311 ]
[SYNCOPE-956] Restoring 'pure' classNames behavior for SAML 2 SP ext
> Allow for scripted customizations
> ---------------------------------
>
> Key: SYNCOPE-956
> URL: https://issues.apache.org/jira/browse/SYNCOPE-956
> Project: Syncope
> Issue Type: New Feature
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Major
> Labels: groovy
> Fix For: 2.1.0
>
>
> The core can be customized in [several
> ways|http://syncope.apache.org/docs/reference-guide.html#customization-core];
> all customizations require to be written as Java classes - which is generally
> good but requires redeploy to be made effective, unless some class reloading
> mechanism is in place (as JRebel).
> By leveraging Groovy, we could overcome such limitation and allow to write
> customizations which can be immediately available for execution at runtime.
> Once implemented in the core, such feature will require editing capabilities
> to be added to console and IDE plugins.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
