I have a question regarding the resourceManager.update();
If you set the localechain it already executes the update event so this class does the update function twice and it dispatches the change event two times.

Is there a reason for the resourceManager.update(); to execute in this class?

I want to load a property file dynamically and create a resource bundle. is there any way for this..??

I know we can use resourceManager.loadResourceBundle(), but it’s to load swf file… similarly is there any approach for .property or .xml file…?

So my setters are:

public function set resourceBundle(value:String):void
{
// set new resource bundle
if (_resourceBundle != value)
{
_resourceBundle = value;
_resourceBundleChanged = true;
invalidateProperties();
}
}

And

override protected function commitProperties():void
{
super.commitProperties();

Thank you for the words of encouragement and for noticing my little project. By the way, I did abandon Israfil long ago in favor of your much more capable flex-mojos plugin. When I first started working in Flex and Maven, I was new to both technologies and back then the Israfil plugin seemed easier for someone to get up and running without much effort and without in-depth knowledge. But it wasn’t long before I started running into more complex needs that the Israfil plugin just could not support. I started extending it to meet my needs and that was OK, but I did not like the idea of having this one off customization and the demands for change kept growing. Ultimately I delved into the flex-mojos plugin and converted all out projects to use it instead. It did take a more in depth investment of time and learning curve to get up and running with the flex-mojos, but I can say looking back, there are no regrets. Flex-mojos have provided me with a solution for every curve I have thrown at it and we have a fairly complex build. Also its support for pulling down the flex compiler artifacts rather than being dependent on a local install of the flex SDK was very nice since we use both Windows and Linux platforms for Maven builds.

So, let me take this moment to extend a BIG THANK YOU for all your efforts on that project!

I agree that dependency management in the Flex development world is a bit out of sorts and including non-maven-hosted flex dependencies is a pain. Your project and M2 repository hosting the Flex SDK artifacts is a huge benefit for all of us Flex-Mavenites, I certainly wish Adobe and the community would embrace Maven. I will follow up on your zipped artifacts support topic on the Google code site, I like the idea and will do what I can to include it

I do like your initiative, specially on the flex universe it is a real pain to find anything on maven central… nor Flex SDK nor 3rd party libraries are deployed there.

FWIW, I started on maven plugin development on a much similar way, but instead of israfil I started hacking servebox… eventually I figured that was too much pain and the project seemed death, so I decide to start a fresh one.

For sure I will advice flexmojos users about your plugin and may use it in the future if it begins to support zipped artifacts (I wrong a ticket on code google).

Says here http://help.adobe.com/en_US/Flex/4.0/UsingSDK/WS2db454920e96a9e51e63e3d11c0bf69084-7f27.html#WS2db454920e96a9e51e63e3d11c0bf6119c-7fe1

I agree and wish there were better tooling for the localization effort.
Take a look at this post, I personally don’t like the idea of explicitly defining a resource manager string lookup every single place I need to perform localization, so I take this approach:
http://www.savage7.com/index.php/2009/08/adobe-flex-3-how-to-create-localized-ui-component-control/