[OS-JIRA] Created: (WOL-699) No way to tweak binding validation for keys

From: Pierce T. Wetter III (JIRA) ("Pierce)
Date: Wed Jan 02 2008 - 16:43:37 EST

  • Next message: Pierce T. Wetter III: "Re: Issue with Binding validation"

    No way to tweak binding validation for keys
    -------------------------------------------

                     Key: WOL-699
                     URL: http://issues.objectstyle.org/jira/browse/WOL-699
                 Project: WOProject/WOLips
              Issue Type: Bug
        Affects Versions: WOLips 3.3.2.* (nightly build please specify)
                Reporter: Pierce T. Wetter III

    So I have a bunch of wod files where the validator kvetches about valid keys.

    That's the key I'm binding to, not the value I'm binding.

    Example:

            xmlns:m = "http://paceap.com/soap/";

          or

            transactions..ountTunnel = "AdminTransactionSummary;encryptedPrimaryKey;assetID";

    Now the validator lets you put regexes in there for valid _values_ but not valid keys.

    Similarly, you can put // VALID on a case by case basis.

     But those are for _values_, not keys.

     So I was wondering if the //VALID tweak could be applied to both sides, and/or have the validator rules apply to both sides?

    A checkbox on the rules (apply to key) would also work, but separate rules for values vs. keys would be better presentation. I actually thought the validation rules were broken for the longest time until I realized it was only looking at the _values_, not the _keys_; 99% of my values validates, its the strange key formats that bitch. But I'm stuck with the strange key formats, because we have keys that are based on the results of previous key paths. That is, "transactions..ountTunnel" comes about because we pass in "transactions.@count" to another binding. Plus the occasional legal binding like "SOAP-INC".

    While I suppose you could make the rules much more complex, and have:

    Component Key Value

    In practice, you'd need to have a "NULL" match to indicate regular validation. That is:

    .*SOAP.* xmlns:m <blank>

    Would say "the key is valid, but dunno about the value", while

    .*SOAP.* xmlns:m .*

    Would mean it wouldn't even look at the value.

    But that seems like it would make the rules unnecessarily complex. Better to either have two lists, one for keys and one for values with //VALID being a global override.

    -- 
    This message is automatically generated by JIRA.
    -
    If you think it was sent incorrectly contact one of the administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa
    -
    For more information on JIRA, see: http://www.atlassian.com/software/jira
    



    This archive was generated by hypermail 2.0.0 : Wed Jan 02 2008 - 16:44:30 EST