You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@geode.apache.org by "Darrel Schneider (Jira)" <ji...@apache.org> on 2019/10/25 22:13:00 UTC

[jira] [Resolved] (GEODE-7267) ClassName validation code should be in a validator or removed

     [ https://issues.apache.org/jira/browse/GEODE-7267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Darrel Schneider resolved GEODE-7267.
-------------------------------------
    Fix Version/s: 1.11.0
       Resolution: Fixed

The fix for GEODE-7266 also fixed this ticket.

> ClassName validation code should be in a validator or removed
> -------------------------------------------------------------
>
>                 Key: GEODE-7267
>                 URL: https://issues.apache.org/jira/browse/GEODE-7267
>             Project: Geode
>          Issue Type: Bug
>          Components: management
>            Reporter: Darrel Schneider
>            Priority: Major
>             Fix For: 1.11.0
>
>
> org.apache.geode.management.configuration.ClassName has a method isClassNameValid that is public and is called from the constructor to validate the class name. This validation should be reviewed for the v2 api. Should it be moved to a validator?
> Also does the management external apis need to expose it as a method users can call?
> Also should we be implementing code to verify the syntax of a legal java class name or deferring to the jvm for this?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)