[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1206) improve i18n in seam-gen

[Anthony Whitford (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBSEAM-1206?page=comments#action_12364157 ] 
            
Anthony Whitford commented on JBSEAM-1206:
------------------------------------------

I remember the eclipse-plugin based seam-gen used to do this -- labels for each field would be expressions:  #{messages.className_fieldName}

Then, all you had to do was update the messages bundle if you wanted to override the default translation (and of course create new message bundles for different languages).  It would guess correctly most of the time (for English) because a camel case translation works most of the time ("aFieldName" -> "A Field Name").  The best part was that you just had to update one message bundle instead of editing 3 xhtml files per business domain object.

The HUGE benefit of this strategy is that seam-gen creates a truly localizable application.

(I am surprised that this feature went away.)


> improve i18n in seam-gen
> ------------------------
>
>                 Key: JBSEAM-1206
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1206
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Tools
>    Affects Versions: 1.2.1.GA
>            Reporter: Pierre Raoul
>         Attachments: i18n.zip, seam-gen.diff, seam-gen.zip
>
>
> It would be great that seam-gen will generate crud pages and classes for an existing Entity class:
> - with all the literals replaced with #{messages['key']}
> - and i18n default messages generated

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