[
https://issues.apache.org/jira/browse/SYNCOPE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16492325#comment-16492325
]
Francesco Chicchiriccò commented on SYNCOPE-1317:
-------------------------------------------------
Removing all schemas is definitely an edge use-case; anyway, the Admin Console
should be robust enough to handle such cases too.
I see you manually added back a schema via the underlying database; FYI, you
could have better done this through the REST interface.
> 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
> 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)
