[infinispan-issues] [JBoss JIRA] (ISPN-7228) Administration console - creating wrong schema doesn't show error message

[Vladimir Blagojevic (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-7228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13353772#comment-13353772 ] 

Vladimir Blagojevic commented on ISPN-7228:
-------------------------------------------

[~anistor] I get it! However, we don't have methods getFileErrors and getFilesWithErrors exposed to DMR, hence our hands are tied. Until we do, there is little [~ryanemerson] and I can do here. [~anistor] can you perhaps expose an operation that would check syntax and semantic errors of a registered protobuf? That way we can register proto but and then query if there are any errors. What would also work changing the semantics of registerProtofile/Schema so we can get these errors returned right away but I am not sure what is the impact of such a change and/or if it is doable. Thoughts [~anistor] and [~NadirX]? 

> Administration console - creating wrong schema doesn't show error message
> -------------------------------------------------------------------------
>
>                 Key: ISPN-7228
>                 URL: https://issues.jboss.org/browse/ISPN-7228
>             Project: Infinispan
>          Issue Type: Bug
>          Components: JMX, reporting and management
>    Affects Versions: 9.0.0.Alpha4
>            Reporter: Roman Macor
>            Assignee: Vladimir Blagojevic
>            Priority: Minor
>         Attachments: ISPN-7228.txt
>
>
> Click on cache container -> Configuration -> Schemas -> Add -> Fill in incorrect scheme: (schema name: wrong_schema, Schema: nonsense)
> Result: The dialog is closed and no schema is created.
> Expected message:
> Error There has been an error executing the operation: DGISPN0118: Failed to invoke operation: org.infinispan.protostream.DescriptorParserException: java.lang.IllegalStateException: Syntax error in nonsense.proto at 1:9: unexpected label: nonsense 



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)