The error that "No class registered for interface ‘mx.styles::IStyleManager2′"

January 31st, 2008 Ntt.cc

When I compiled “flex3_sdk ->samples ->explorer ->containers ->SimpleTitleWindowExample.mxml” with mxmlc and run it,i got the error below:

Error: No class registered for interface ‘mx.styles::IStyleManager2′.
   at mx.core::Singleton$/getInstance()
   at mx.styles::StyleManager$/get impl()
   at mx.styles::StyleManager$/http://www.adobe.com/2006/flex/mx/internal::initProtoChainRoots()
   at simpleTitleWindowExample/http://www.adobe.com/2006/flex/mx/internal::_SimpleTitleWindowExample_StylesInit()  at SimpleTitleWindowExample()

Maybe it’s too simple for you,but i spend too much time fixing this error. I found there was a comment like below:

<?xml version="1.0" encoding="utf-8"?>
<!-- Simple custom MXML TitleWindow component.
     The TitleWindowApp application displays this component. 
     You cannot run it independently. -->

Yes,it denpends on another mxml and can not be directly run.:)

Share and Enjoy:

---

• 
• 
• 
• 
• 
• 
• 
• 
• 

If you enjoyed this post, please consider to leave a comment or subscribe to the feed and get future articles delivered to your feed reader.

Posted in Flex Tags: flex, interface, MXML, mxmlc, SDK

Enjoy this Post? Subscribe to Ntt.cc   RSS Feed      Email Feed Follow us

You might also want to read...

• automatically create an Ant build file from your Flex Builder project with Flex2Ant (0)
• Using Debugger And Print To Debug Your ActionScript Under Linux (4)
• How to load an image into our Flex application from URL(with source) (13)
• sample code which guide you on how to communicate between Flex and Php (2)
• how to add the Logical operator in MXML (0)

« automatically create an Ant build file from your Flex Builder project with Flex2Ant

JavaScript function-Splits the string by given separator and returns an array with trimmed items »

You can leave a response, or trackback from your own site.

6 Responses to “The error that "No class registered for interface ‘mx.styles::IStyleManager2′"”

1. Sam Dean says:

   July 28, 2008 at 9:22 pm

   Hi,

   I ran into this same problem whilst compiling an actionscript project. I fixed it by adding the line :

   Singleton.registerClass(“mx.styles::IStyleManager2″, Class(ApplicationDomain.currentDomain.getDefinition(“mx.styles::StyleManagerImpl”)));

   as the first line in my constructor.

   Hope this is useful,

   Sam

   Reply
2. hasselquist.net » Blog Archive » Set the ANT_OPT for flex ant tasks to avoid the error “out of memory” threw by Flex Builder when building a huge project says:

   August 21, 2008 at 10:08 am

   [...] The error that "No class registered for interface ‘mx.styles::IStyleManager2′"… [...]

   Reply
3. Don’t run/debug a flex compent under Flex Builder « :maohao: says:

   March 17, 2009 at 2:31 am

   [...] reading this, I found out I was unintentionally running/debugging a flex component instead of a flex [...]

   Reply
4. Quantium says:

   October 29, 2009 at 12:32 am

   Hi all,

   Thanks Sam, I’ve already done the Singleton.registerClass thing. But now I have a new issue, When i compile I see ‘value is not a function’ when Singleton calls c['getInstance']() function.

   That function is there in IBrowserManager but still don’t reconigsed.

   Reply
5. whois says:

   June 11, 2010 at 8:37 am

   @Quantium

   Same issue on my part.=( can’t figure out.

   Reply
6. Daerd says:

   January 21, 2011 at 6:43 pm

   I have this very same problem. From doing a bit of Googling, I’ve come to understand that the problem seems to be that one shouldn’t compile/run an AS3 application from a component (a subclass of mx.controls.* or, in my case, from a MovieClip), lest you will have this error. Compile/run from your Application class instead.

   Not sure if this will really solve the problem (since I’m a n00b at AS3 and I haven’t got to testing it yet) but it seems quite logical to me!

   Reply