You've got three major technologies there. It depends on if you're learning, or if you're knee deep in a project.
Really, you should learn a bit about each one, and then look towards integrating them. So, learn the basics of JSF, then Spring, and then Hibernate, and you'll know all of the config files that are needed. From there, look in the back of a big Spring book, and it will talk about integrating the pieces together.
In my humble opinion, one of the big problems with these frameworks is that people do just that - they try and build these monolithing, framework bloated applications, without any real understanding or appreciation of what each framework does. You really need at least a basic understanding of each if you plan on integrating them all together.
Cameron Wallace McKenzie wrote:You've got three major technologies there. It depends on if you're learning, or if you're knee deep in a project.
You really need at least a basic understanding of each if you plan on integrating them all together.
Unfortunately, the order of the day is to take people with about 2 years experience, shove an IDE at them, and expect them to use the IDE's wizards to create and maintain these complex projects. Which pretty well explains why so many websites these days are so flimsy.
The exact set of configuration files when combining complex technologies like these can vary considerably. At a minimum, you'd find the faces-config and Spring bean definition files, but they can also pull in side files as needed for special featured, and/or be renamed or split to make a large project more modular. Hibernate can be configured quite differently depending on whether it's being used in traditional or JPA modes and whether you're using XML or annotations (or both).
Customer surveys are for companies who didn't pay proper attention to begin with.