You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Christoph Bussler (JIRA)" <ji...@apache.org> on 2007/08/03 00:18:52 UTC

[jira] Created: (OPENJPA-306) Validation for Configuration Properties

Validation for Configuration Properties
---------------------------------------

                 Key: OPENJPA-306
                 URL: https://issues.apache.org/jira/browse/OPENJPA-306
             Project: OpenJPA
          Issue Type: New Feature
          Components: kernel
         Environment: All supported environments
            Reporter: Christoph Bussler
            Priority: Minor


In the general case, configuration properties have constraints on values they can have. Some of these constraints are implemented today, for example enumeration of possible values for a given property of type enumeration. However, other properties, like lockTimeout of type integer do not (yet) have constraints defined and implemented that can be checked against.

For example, when the lockTimeout property is set it is undefined currently what permissible values are. The default is -1, but is -2 a possible value? Is 0 a possible value? Are all the natural numbers possible values?

What would be required is a validate() method that given an intended value for a property returns true/false indicating if the provided value for the property is a valid one. If this is done uniformly across all properties it is possible to check the property's value for consistency before attempting deployment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (OPENJPA-306) Validation for Configuration Properties

Posted by "Patrick Linskey (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/OPENJPA-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517397 ] 

Patrick Linskey commented on OPENJPA-306:
-----------------------------------------

This issue contains two concepts:

1. the addition of a Value.validate() method

2. improved implementation of Value.validate() for various of the configuration settings

I think that #1 is the short-term need, and #2 will be an ongoing effort.

> Validation for Configuration Properties
> ---------------------------------------
>
>                 Key: OPENJPA-306
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-306
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: kernel
>         Environment: All supported environments
>            Reporter: Christoph Bussler
>            Priority: Minor
>
> In the general case, configuration properties have constraints on values they can have. Some of these constraints are implemented today, for example enumeration of possible values for a given property of type enumeration. However, other properties, like lockTimeout of type integer do not (yet) have constraints defined and implemented that can be checked against.
> For example, when the lockTimeout property is set it is undefined currently what permissible values are. The default is -1, but is -2 a possible value? Is 0 a possible value? Are all the natural numbers possible values?
> What would be required is a validate() method that given an intended value for a property returns true/false indicating if the provided value for the property is a valid one. If this is done uniformly across all properties it is possible to check the property's value for consistency before attempting deployment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.