I would argue that an application scoped seam component, with defaults set in
seam.properties, and a quick crud, would be ideal for this. Certainly quick to
develop - but changes would be lost between redeploys I guess.
View the original post :
http://www.jboss.com/index.html?module=bb&op=view
Ok, perhaps I have to be more precise. The configuration properties I'm talking
about do not belong to the seam configuration of components. I'm talking about
application specific parameters controlling for examples the behaviour of
business logic.
Example: A booking application stores all canc
http://jira.jboss.com/jira/browse/JBSEAM-1052
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028329#4028329
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028329
___
jboss-use
I use a different approach: Have seam-dev.properties, seam-prod.properties
(etc.) and use my and script to copy the correct one to
WEB-INF/classes/seam.properties when I do ant war - in fact, I think seam-gen
should probably do this.
View the original post :
http://www.jboss.com/index.html?mod
