You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2018/05/28 06:54:00 UTC
[jira] [Resolved] (SYNCOPE-1317) RuntimeException when remove all
schemas
[ https://issues.apache.org/jira/browse/SYNCOPE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò resolved SYNCOPE-1317.
---------------------------------------------
Resolution: Fixed
This issue was fixed as part of SYNCOPE-1282; Apache Syncope 2.0.9-SNAPSHOT does already handle correctly the edge situation.
> RuntimeException when remove all schemas
> ----------------------------------------
>
> Key: SYNCOPE-1317
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1317
> Project: Syncope
> Issue Type: Bug
> Components: console
> Affects Versions: 2.0.8
> Reporter: Alireza Ranjbaran
> Assignee: Francesco Chicchiriccò
> Priority: Minor
> Fix For: 2.0.9, 2.1.0
>
>
> Dears,
> After removing all schema from \{Configuration > Types > Schemas} I got below error:
> {code:java}
> Unexpected RuntimeException
> Last cause: toIndex = 10
> WicketMessage: Error attaching this container for rendering: [WebMarkupContainer [Component id = body]]
> {code}
> I have added a schema manually into SYNCOPESCHEMA and PLAINSCHEMA and issue has been rectified. It seems there is a bug that prevent loading Schemas when it is empty.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)