nhpvti wrote :
| I've tried custom navigation handler for adding language suffix at the end
of an action, for example: register_en, register_de
|
My custom view handler works seamless with JSF navigation and Seam pageflow and
forces templates names in the form of name_loc.xhtml, for
For those guys out there using postgresql this is how to create a UTF-8 db:
#On linux su to postgres user
su -c su -s /bin/sh postgres
#Create the db user
createuser -d -P -E dbUser
#create the instance
createdb -E UNICODE instance -O dbUser
#To see if it worked:
psql -l
#Results in
perwik wrote :
| but why do this at all when you can have register.xhtml include the locale
specific parts instead?
In order to reduce number of templates to be generated and supported. Besides
CMS contributors should get a big picture in preview mode, ideally the whole
content part in
perwik wrote : Oh, whith object and connections etc. I was thinking of a
database.
|
I have concerns about retrieving static information at runtime from a database,
even using some kind of caching.
Why not to use some standard CMS to produce templates and this way avoid
overhead at
It doesn't work, but something like this would be nicer:
| navigation-rule
| navigation-case
| from-outcomeregister/from-outcome
| to-view-id/register_#{locale}.xhtml/to-view-id
| redirect /
|
that's a great - thanks , I wonder what design pattern do you use with
seam/ejb3.0 in order to retrieve text in different languges from the db to the
JSF pages
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3969196#3969196
Reply to the post :
In CVS version of Seam is SeamCharacterEncodingFilter class. This should make
UTF8PhaseListener obsolete (can someone confirm that?). You must put this in
web.xml:
filter
| filter-nameCharacter Encoding/filter-name
| filter-class
|
perwik wrote : One option would be to see each static content item as one
object and then connect a number of translations to it. Then you show the
translation corresponding to the current locale using the same rules as the
properties files (i.e showing the default locale when the selected
Oh, whith object and connections etc. I was thinking of a database.
Your solution works well with content that is really static. But I'd prefer
some sort of wiki/CMS functionality so that users can edit the content without
access to the .xhtml files (which they shouldn't even have to know or
