4 Replies Latest reply on Aug 26, 2009 4:10 AM by Tony Herstell

    Internationalisation problem with standard JSF messages

    Tony Herstell Master

      I have not used the locale picker seam component for a couple of years and now I return to it for a project; I am having issues with inl8.

      I have, as usual, a file in the WAR project, under src directory, in package nz.co.softwarefactory.risingstars.inl8 called jsfstandarderrors.properties

      Normally when I want to override a JSF message with a more readable one I just find the id and slap a new message in this file. e.g.

      javax.faces.component.UIInput.CONVERSION = error
      javax.faces.component.UIInput.CONVERSION_detail = invalid
      javax.faces.component.UIInput.REQUIRED = required
      javax.faces.convert.DateTimeConverter.CONVERSION = must be a valid date
      #javax.faces.convert.DateTimeConverter.CONVERSION_detail = value must be a datetime

      However since this project needs local support I added to components.xml this setup (as per the manual)

      <international:locale-config default-locale="en" supported-locales="en de"/> <!-- en_GB for GB english etc. -->

      All seems well until I get a standard JSF error message from the site and I then get this

      Unexpected Error Can't find bundle for base name nz.co.softwarefactory.risingstars.i18n.jsfstandarderrors, locale en

      I had assumed it would always default to the base file but it does not.

      I tried adding a jsfstandarderrors_en.properties to no avail.

      Any help would be useful