Tapestry 5
  1. Tapestry 5
  2. TAP5-1319

Need to support property paths for validated field

    Details

      Description

      Current implementation does not support property paths for beans, while the Bean Validation API and Hibernate Validator support this feature.

      In attachment my own implementation of BeanFieldValidator.java with support this feature as well as isRequired() method.

      1. RequiredContextImpl.java
        0.5 kB
        Vladimir Velikiy
      2. RequiredContext.java
        0.2 kB
        Vladimir Velikiy
      3. propertyPathSupport.diff
        7 kB
        Vladimir Velikiy
      4. ImprovedBeanFieldValidator.java
        7 kB
        Vladimir Velikiy

        Activity

        Hide
        Igor Drobiazko added a comment -

        If you want any changes to be applied to the code base you should provid a patch.

        Show
        Igor Drobiazko added a comment - If you want any changes to be applied to the code base you should provid a patch.
        Hide
        Vladimir Velikiy added a comment -

        Patch for property path support attached

        Show
        Vladimir Velikiy added a comment - Patch for property path support attached
        Hide
        Dustin Woods added a comment -

        Does this patch allow property traversal for those marked with @Valid or is that a different issue?

        Show
        Dustin Woods added a comment - Does this patch allow property traversal for those marked with @Valid or is that a different issue?
        Hide
        Vladimir Velikiy added a comment -

        No, this patch allow property traversal for subobjects fields in property paths. For example: organization.address.city.

        Show
        Vladimir Velikiy added a comment - No, this patch allow property traversal for subobjects fields in property paths. For example: organization.address.city.
        Hide
        Jochen Kemnade added a comment -

        This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

        If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.

        Show
        Jochen Kemnade added a comment - This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future. If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.
        Hide
        Jochen Kemnade added a comment -

        We assume this is no longer relevant and therefore close it.
        If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.

        Show
        Jochen Kemnade added a comment - We assume this is no longer relevant and therefore close it. If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.

          People

          • Assignee:
            Unassigned
            Reporter:
            Vladimir Velikiy
          • Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development