블로그 이미지
올해목표 // 10월 어학연수 떠나자~ 자수씨

카테고리

전체글 (1457)
Brand New! (28)
주절주절 (213)
MOT (11)
해외쇼핑 (49)
쇼핑노트 (150)
취미생활 (94)
iPhone (4)
Eclipse (121)
Google (83)
Spring (31)
JAVA (176)
JavaScript (59)
WEB (49)
Database (20)
OS (26)
Tools (8)
Tips (26)
IT정보 (1)
Book (21)
Programming (37)
외부행사 (43)
주변인들 (17)
여행노트 (60)
학교생활 (30)
회사생활 (52)
사회생활 (5)
외국어공부 (12)
잡동사니 (30)
Total
Today
Yesterday
 
11-05 05:27
 

달력

« » 2024.11
1 2
3 4 5 6 7 8 9
10 11 12 13 14 15 16
17 18 19 20 21 22 23
24 25 26 27 28 29 30
 

최근에 올라온 글

최근에 달린 댓글

'War'에 해당되는 글 1건

  1. 2008.12.07 [GWT] Design Doc for 1.6 WAR structure
[원문] http://code.google.com/p/google-web-toolkit/wiki/WAR_Design_1_6

In 1.5, GWTShellServlet served resources directly off the classpath (for public files), or generated files from a temporary location. This has the advantage of allowing fast refresh and resource updating, and making things "easy". However, it has the downside of not leaving the user with something that's easy to deploy.

We will rectify the deployment issue in 1.6 by standardizing GWT around the "expanded WAR format". The two key principles are:

  1. The result of running the GWT compiler (and possibly some associated tools/build rules) will be an expanded WAR directory structure that can be immediately deployed to a Java Servlet Container compatible web server.
  2. Hosted mode will operate using essentially the same format, in the same directory, to ensure that hosted and compiled web applications behave the same.

In 1.6, we always dump all resources directly into the WAR directory, which the server serves directly out of. We automate in hosted mode what a build process would do. This is triggered by the Hosted Browser actually executing a selection script; the selection script (when running hosted mode) forces a hosted mode link. Subsequent GWT.create() calls may cause incremental links.


GWT 1.6 이 보이길래 GWT 1.6 버전 개발 계획인지 알고 냉큼 떡밥을 물었더니 deploy 와 관련된 내용이네요.

내용을 슬쩍 보아하니 머리속에서는 이해가 되는데 번역이 안되네요 ㅋㅋㅋㅋ

아... 영어...




Posted by 자수씨
, |

글 보관함

최근에 받은 트랙백