Unable to resolve a class for ResourceBundle: CairngormMessages

Today I was building an application using Cairngorm 2.2. All was going well and I was very happy with the progress I was making. But then, I started facing this error while compiling the application.

Unable to resolve a class for ResourceBundle: CairngormMessages

From the text of the error it appears that the locale-specific bundle for CairngormMessages is not available/visible.

I made sure that the “locale” folder was available off the root of the project, and that the compiler was using the correct locale setting.

But I found an interim solution to the issue — using Cairngorm.swc, rather than the actual source of Cairngorm (which I was using) makes the error goes away.

So, for now I’m on my way by using Cairngorm.swc. But I still need to figure out why the error occurs in the first place.

Any thoughts?

11 thoughts on “Unable to resolve a class for ResourceBundle: CairngormMessages”

  1. Thanks Muzak. I’ve looked at the comments, and tried to add the locale path as suggested. But doesn’t seem to do the trick.

    The only way I can get it to go is by using the SWC — which is an acceptable solution at the moment. It is just that I like to use the source when developing so that I can actually see what the framework is actually doing.

  2. Indy,

    I also had this problem, but cannot remember the working solution. Mine is working now. Sorry I did not blog it at the time now. Anyway, I set up Cairngorm as a Project in my workspace. In the cairngorm project, I have:
    Library path – ${FRAMEWORKS}/locale/{locale}
    Source path – locale/{locale}
    and also a locale/en_US directory path with CairngormMessages.properties in there.

    In my project that uses cairngorm I "Add Project" under Library path.

    Hope this helps you.
    Tony

  3. Thanks for your comment Tony. It is very helpful. Where are you based? I looked at your blog, but couldn’t find anything about you. You have some good stuff there!

  4. Thanks Indy,
    I am out of Southern California. I have been using Flex for about 4 months now. I hope you were able to get your problem solved. If not, I would set up a new project trying to use Cairngorm the way you had it and see where your settings may have broke.

    Tony

  5. Did you ever get this to work? I am having the same problem but I am not really understanding Tony’s solution?
    I downloaded the Cairngorm source files, unzipped it to a location and then I tried to create a Flex Library project. Is that what I need to do ? I am still very new to this and would appreciate if someone told me exactly what to do if you want to use the source code instead of the swc for development purposes.
    Cheers
    Prem

  6. You can do either of the following:

    – Use Cairngorm.swc, rather than the actual source code of Cairngorm

    – If you want to use Cairngorm source code, then you can:

    a) copy the locale folder in the root of your Flex Builder project.
    b) the Flex compiler path in Flex Builder would look like this:

    -source-path+=locale/{locale} -locale=en_US –services=[PATH_TO_services-config.xml]

    You’d need to replace [PATH_TO_services-config.xml] with the path to services-config.xml that you want to use.

    That should do it.

    Let me know how you go.

  7. I realize this is an old thread to follow, but since flexcairngorm is still a good resource and there is very little info on the topic of this error message (that probably occurs a fair amount), I will put in my 2 cents. The error message is:

    unable to resolve resource bundle CairngormMessages for locale _us

    If you get this message, a quick solution is to use the latest swc for flexcairngorm (mine is called UM_Cairngorm_2.2.1.swc) and be sure there is no other Cairngorm version in your flex build path. Furthermore, manually check your .actionScriptProperties config textfile and remove any entries that might be a problem. That should make it go away. Hope this helps.

Leave a Reply to Indy Nagpal Cancel reply

Your email address will not be published. Required fields are marked *