Misunderstandings about using Flex, tomcat, JRun, ColdFusion, IIS, and ASP. NET!

Misunderstandings about the use of FLEX, JRun, ColdFusion, IIS, and ASP. NET! (Flex1.5 only)

I haven't touched flex for nearly two years. Recently, several users have asked about flex, JRun, tomcat, ColdFusion, IIS, and ASP. net, it is best to achieve multiple functions with only one server. This makes me feel very strange. At present, the flex versions of mm are all in Java, so they can only run on Java servers, for example, Tomcat and JRun (ColdFusion depends on standlone, war, and ear), while IIS is only an HTTP server (JRun and tomcat also provide HTTP service functions, so the combination of meaning is very pale), is not to run flex, the so-called IIS can run ASP. net, that is required.. NET Framework, and IIS only forwards the HTTP request of Asp.net.. net. IIS itself does not process Asp.net. Therefore, the so-called combined use means that IIS forwards HTTP requests to Java servers such as Tomcat and JRun (or. to implement multiple functions such as flex, JSP, HTTP, and Asp.net, multiple servers must be supported. Not all configurations of a server can be implemented! What's more, we think that combined with the aspx.net program, we can directly control the interaction with the mxml program! Ah! In the end, interaction is the way that flex supports HTTP service, WebService, and remoteservice.

At the same time, I also explained that flex is only a Runtime library or web application used to process mxml files. Its Runtime Library is flex. therefore, it can be deployed on any compatible JSP server, such as Tomcat, WebLogic, websphere, JRun, and JBoss. ColdFusion is also a Runtime library or web application, cfusion is the Runtime library used to process files of the CFML type. war, the so-called standalone version of ColdFusion only sets JRun and cfusion. war is packaged and installed together, so there is no combination of flex and ColdFusion!

Finally, let me talk about the operating configuration of Flex. The reason is that there are many strange configurations in the operating environment of Flex on the Internet! Flex needs a JSP server. Of course, for flex development, we only need to find a Java Server that occupies as few resources as possible and has the highest performance as possible. I think Tomcat should be the first choice, and then it will be very easy, download the flex installation file from mm. After installation is complete, put the flex file in the installation directory. copy the war file to the webapps directory of Tomcat. The configuration is complete and simple. There are so many people discussing the tedious and resource-consuming configuration methods on the Internet! Start Tomcat directly now (you do not need to start it again after it is started). Tomcat will automatically set this flex. war is deployed. The flex directory is automatically created under the webapps directory. You can write a helloworld. put the mxml test program in the automatically created flex directory and open the browser http: // localhost: 8080/flex/helloworld. mxml to check whether it is running normally! The same is true for deploying to other JRun and WebLogic servers. Why is it so simple? Because Flex is a Web application in the J2EE specification, you should understand the file name Flex. War. To run the sample that comes with Flex, copy the sample. War file under the installation directory to the webapps directory.