Files changed (1)
-However, they are all very similar and usually allow deployment of WAR file or exploded directory web applications.
-Some cloud environments have typical Java application servers available for hosting, while others such as the Google App Engine run a bit differently.
-In this chapter, we’ll discuss how to deploy web-based Jython applications to a few of the more widely used Java application servers.
-We will also cover deployment of Jython web applications to the Google App Engine and mobile devices.
-Although many of the deployment scenarios are quite similar, this chapter will walk through some of the differences from container to container.
+"클라우드"에 배포하는 것은 완전히 다른 시나리오이다. 어떤 클라우드 환경은 호스팅이 가능한 일반적인 자바 애플리케이션 서버를 갖추고 있지만, 구글 앱 엔진과 같이 조금 다르게 동작하는 것들도 있다.
-In the end, one of the most important things to remember is that we need to make Jython available to our application.
-There are different ways to do this: either by ensuring that the *jython.jar* file is included with the application server, or by packaging the JAR directly into each web application.
-Placing the *jython.jar* directly into each web application is a good idea because it allows the web application to follow the Java paradigm of “deploy anywhere.” You do not need to worry whether you are deploying to Tomcat or Glassfish because the Jython runtime is embedded in your application.
+*jython.jar*\ 를 각 애플리케이션에 직접 갖다놓는 것은 좋은 방법인데, 그것은 웹 애플리케이션이 어디에나 배포 가능하다는 자바의 패러다임을 따르기 때문이다.자이썬 런타임이 애플리케이션에 내재하기 때문에 톰캣에 배포하든 글래스피쉬에 배포하든 걱정할 필요가 없다.
-Lastly, this section will briefly cover some of the reasons why mobile deployment is not yet a viable option for Jython.
-While a couple of targets exist in the mobile world, namely Android and JavaFX, both environments are still very new and Jython has not yet been optimized to run on either.
-As with any Java web application, the standard web archive (WAR) files are universal throughout the Java application servers available today.
-This is good because it makes things a bit easier when it comes to the “write once run everywhere” philosophy that has been brought forth with the Java name.
-The great part of using Jython for deployment to application servers is just that, we can harness the technologies of the JVM to make our lives easier and deploy a Jython web application to any application server in the WAR format with very little tweaking.
+애플리케이션 서버에 배포함에 있어서 자이썬이 훌륭한 점은, JVM 기술을 활용하여 우리의 삶을 편하게 할 수 있으며, 약간의 조정을 거쳐서 자이썬 웹 애플리케이션을 어떠한 애플리케이션 서버에든지 배포할 수 있다는 점이다.
-If you have not yet used Django or Pylons on Jython, then you may not be aware that the resulting application to be deployed is in the WAR format.
-This section will discuss how to deploy a WAR file on each of the three most widely used Java application servers.
-Now, all application servers are not covered in this section mainly due to the number of servers available today.
-However, you should be able to follow similar deployment instructions as those discussed here for any of the application servers available today for deploying Jython web applications in the WAR file format.