This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
Hello. Just wanted to know whether this pattern has some major drawbacks in large J2EE applications. Currently I am looking at reading all the constant data from either a properties file or the database. For now the constant data is stored in static fields in all the classes from my application. The only drawback is that I have to keep using the ConstantDataManager everywhere in the application and that the static fields do not make as much sense as when stored in the corresponding classes .
Do you have experience with implementing this pattern ? It looks to me as I have a good solution with this pattern. PS: I am working with Spring & Hibernate if this helps.
Better, faster, lighter Java ... you mean Ruby right ?
SCEA5,SCBCD1.3,SCWCD5,SCJP1.4 - memories from my youth.
What problem are you trying to solve by using property files or a database?
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Don't know. However at this point can't afford to take these chances .. I am not allowed to take such a decision. A compromise sounds as the best solution. (that is develop repositories for constant data per modules/sections of the application). Anyhow for now just canceled any changes due to risks involved.