[JBoss Seam] - Re: seam-gen : old issues
by atao
in target generate-entities:
- a template is used to put the list of all the "root" keys needed by an entity in a text file; this template combines the structures of list.xhtml.ftl and edit.xhtml.ftl to be sure to cover all the messages needed by an entity
- and an other template will put the list of all the entity name in an other text file
- then an ant task will read all theses files and generate a unique file for each language with all the final keys and the messages associated
To do the job, this last task will read:
- </locale-config> in faces-config.xml to get the list of languages to deal with
- a xml file provided by the developper to get all the translations wished.
If a translation is missing, the task will create a default message from the key, e.g.:
Worker.grossWage -> entity.worker.gross.wage.label=Gross Wage
I'm ok to use any straight way to iterate on many entities to extract all the keys needed and put them directly in a unique file.
In my first patch I used fmpp library to do this, but Seam team asked me to do without it, then the current solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093113#4093113
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093113
18Â years, 7Â months
[EJB 3.0] - Passivation-can its time of occurance be controlled?(4.2.1.g
by konkimalla
We use a stateful session bean, which opens a socket connection. It is understood that during the passivation this connection needs to be closed, otherwise the connection becomes hung state and becomes useless during the next garbage collection time. So, during activation we are reopening the connection and everything works well.
I observed that in 4.2.1.ga, passivation happens approximately 6 to 10 mins. I have seen the variation in the time. I thought of removing the passivation, so edited the following file
ejb3-clustered-sfsbcache-service.xml with to have false. Even after running using "-c all" option, I see passivation is happening; I see logs showing that the state is getting stored in a file.
1) Is there any way I can stop the passivation?
2) Is there any way to increase the time of passivation to "x" mins.
This is becoming a bottleneck to our requirement. Hence, Please give me a solution.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4093111#4093111
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4093111
18Â years, 7Â months