Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 6.0.7-5
    • Fix Version/s: 6.0.7-6
    • Component/s: examples
    • Labels:
      None

      Description

      Today I tried to create a new customer/user for Duke's Forest, for the first time in quite a while, and typed a password that was too short. Instead of an error message in the little square I got

      {person.password}

      I tried using incorrect values for some of the other fields and got the same problem – all that was displayed was

      {person.email}

      or

      {person.firstname}

      Apparently the validation messages, which are in dukes-resources.jar, are not being found even though dukes-resources.jar is bundled in dukes-store.war.

      In the dukes-resources.jar file the messages are in java/ValidationMessages.properties and java/ValidationMessages_es.properties.

      In dukes-tutoring, the messages are in dukes-tutoring-war/src/java and are built into the WAR file, in WEB-INF/classes/ValidationMessages.properties etc.

      So Eric and I copied the validation messages into dukes-store/src/java, and after redeployment the messages appear just fine.

      Are the validation messages needed anywhere besides dukes-store? I don't believe any entities are created in dukes-shipment, so removing them from dukes-resources and putting them into just dukes-store might be sufficient.

      I am about to check in some fixes for serialVersionUID (JAVAEETUTORIAL-107) and other cosmetic changes (changing StringBuffer to StringBuilder, adding @Override, line breaks, other NetBeans nits) and was checking to see if I had broken anything. But the same thing happens with the existing version on my other machine, so those fixes I am making haven't changed any behavior.

        Activity

        Hide
        William Markito added a comment -

        That's right Kim, I've run a couple of tests here and that's the same behavior I'm experiencing.

        Also, this issue happened with other bundle messages (Bundle_en.properties...) and that's the reason the file is copied into dukes-store and dukes-shipment, so they can share the same labels for form fields. For some reason, I thought that using the resources project to share the Validation messages were working despite my experience with Bundle.properties.

        So we can remove them from the dukes resources project.

        Thanks for catching that.

        Show
        William Markito added a comment - That's right Kim, I've run a couple of tests here and that's the same behavior I'm experiencing. Also, this issue happened with other bundle messages (Bundle_en.properties...) and that's the reason the file is copied into dukes-store and dukes-shipment, so they can share the same labels for form fields. For some reason, I thought that using the resources project to share the Validation messages were working despite my experience with Bundle.properties. So we can remove them from the dukes resources project. Thanks for catching that.
        Hide
        Kim Haase added a comment -

        Committed changes at revision 1040.

        Show
        Kim Haase added a comment - Committed changes at revision 1040.

          People

          • Assignee:
            William Markito
            Reporter:
            Kim Haase
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: