在Eclipse中找不到文件

Question

I have an eclipse JSF example where the ExampleController class cannot find the Bundle.properties file. Here is the dynamic web project snapshot that was used to create the JSF project,

Here is a snapshot of the project file structure. You can see the bundles file in properties folder,

Here is a snapshot of the class code. Notice the file name in the getBundle methode,

@ManagedBean(name = "exampleController")
@RequestScoped
public class ExampleController {
    private String exampleProperty;

    * Creates a new instance of ExampleController
    */
    public ExampleController() {
        exampleProperty = "Used to instantiate the bean.";
        FacesMessage facesMsg = new FacesMessage(FacesMessage.SEVERITY_INFO, 
                        ResourceBundle.getBundle("WebContent/properties/Bundle.properties").getString("ExampleMessage"), null);
    FacesContext.getCurrentInstance().addMessage(null, facesMsg);
}

Finally, here is a snapshot of the error when I run the code against the tomcat server,

I have tried several combinations of file names but continue to get file not found errors when the server runs. What am I missing?

Best Regards, Steve Mansfield

Answer 1

Try to play with the path. The "WebContent" in your path does not seem right. Usually the resource path gets resolved relatively to WEB-INF or current class-file location. You could also try to put your properties directory in several places, to see if it gets picked up in one of those. :)

Also if you could get your hands on where the built project is actually run from "physically" (if it is not from these very files) maybe you would find out the properties file does not get copied with your other files. (Do you have Deployment Assembly in your Project settings? If so, check it out.)

UPDATE: If you simply need to open a properties file, check this one out: getResourceAsStream() is always returning null ...I don't know if your folder is special in some way tho.

Most often when Tomcat starts acting weirdly in Eclipse I find out that Deployment Assembly is f****d up. (Happens with Mavenized projects. Eclipse and m2eclipse aren't the best friends it seems.)
Such situation fits the scenario "works when deployed to production server, does not when run from within Eclipse."