About Flex.messaging.MessageException:Cannot Create class of type ' XXX '. Type ' XXX ' not found.

The recent project team has been busy with other things, for a long time did not study flex-related technology, today idle to do nothing, want to reconsider the original completed Flex Web program, unexpectedly JBoss in the start, inexplicably strange direct error:

caused by:flex.messaging.MessageException:Cannot create class of type

' Com.blaze.BaseTemplateBlazeService '.

Type ' Com.blaze.BaseTemplateBlazeService ' not found.
At Flex.messaging.util.ClassUtil.createClass (classutil.java:66)
At Flex.messaging.factories.JavaFactoryInstance.getInstanceClass (javafactoryinstance.java:110)
At Flex.messaging.factories.JavaFactoryInstance.createInstance (javafactoryinstance.java:96)
At Flex.messaging.factories.JavaFactory.createFactoryInstance (javafactory.java:114)
... 148 more

It is very strange, the program has not changed, the configuration has not changed, in the end why so?

Nonetheless, the program was carefully examined and the flex-related configuration files

Messaging-config.xml, Proxy-config.xml, Remoting-config.xml, Services-config.xml

In fact The main is remoting-config.xml, but this file does not change, and the error is still, its information hint is also obvious, that is, the response class file is not found, and carefully check the packaging of the Web-inf directory under the Classes folder, found that the class file is already there , really is to let people ecstasy, in the end what fault.

In fact, the program has not changed, the configuration has not changed, the only possibility is that the environment has changed, Since the other applications have been developed with JBoss-4.2.3 during this time, the configuration changes to JBoss itself may be unavoidable, and if this is the case, it would be impossible to be able to determine the JBoss problem, unless JBoss recovers.

Back and beg second, a different version of the JBoss test (4.2.2), this test, it does not matter, and really found the crux of the problem.

Report the other errors directly:

Java.lang.UnsupportedClassVersionError:Bad version number in. class file

The original version of the class file is inconsistent, that is, the JDK version of the compilation environment, and the JDK version of the operating environment is not unified caused by ...

Turn back, reposition, sure enough.

The compiler Java Complier version is JDK 1.6, and the JBoss running JDK set in MyEclipse is 1.5 ...

Damn, it's probably this time. During the development process, the configuration was made when debugging other projects, and forgot ~

At least JBoss-4.2.3 should also give a definite hint. Don't let a person become a husband and two monks ...

Modified JBoss running JDK to keep the version unified, sure enough.

This is a long memory.