Many would think at this point I am talking about better AJAX support in the core.很多人會認為在這一點上我所說的更好的Ajax的支持,在核心。 While we do need better support for AJAX and I am not talking about DWR, I don’t think that’s what ails Java in its quest for being .同時,我們確實需要更好地支持Ajax的,我不是在談論dwr ,我不認為這是什麼ails Java在追求福祉。 At the end we will look at two ways in which we can overcome this problem.在為此,我們將看看兩種方式,使我們可以克服這個問題。

Java is taking a beating in better mass adoption against PHP simply because it is harder to setup in web hosting environment. Java是採取毆打,在群眾更好地通過對PHP的簡單,因為它是難以安裝在Web託管環境。 PHP and even Ruby is available as an Apache module which is very trivial to setup and use. PHP和紅寶石,甚至可作為Apache模塊這是非常微不足道的安裝和使用。 JSP / Servlets on the other hand is much harder to integrate with Apache. JSP中/ / Servlets在另一方面是更加難以整合與Apache 。

Why Apache is the the key to Web 2.0 adoption? 為什麼阿帕奇是關鍵的Web 2.0通過?
Apache is the most popular web server, known for its stability and ease of use. Apache是最流行的Web伺服器,已知其穩定性和易用性。 It is cross platform.這是跨平台。 Most Web 2.0 companies and products rely on Apache as their web server and for right reasons.大多數Web 2.0的公司和產品依賴於他們的Apache Web Server和右的原因。

What are the problems of Java in Apache Integration? 有什麼問題的Java在Apache整合?
Complexity in short.複雜性在短期內。 Tomcat is probably the most popular JSP, Servlet container for most organizations.雄貓可能是最流行的的JSP , Servlet的容器,大多數組織。 Tomcat is free (which aids its popularity) and developed under the Apache organization.雄貓是免費的(即艾滋病的受歡迎程度)和發展下的Apache組織。 I would have expected both these products to be tightly integrated.我想,預計這兩項產品被緊密集成。 In reality it is a nightmare from hell to even begin.在現實中這是一個來自地獄的夢魘,甚至開始。 I wouldn’t say there aren’t any documents.我不會說是沒有任何文件。 There are few少數的 confusing混亂 ones which leads to more questions than answers.那些導致更多的問題多於答案。 What we lack is a clear simple guideline to integrate the two.我們缺乏的是一個明確的指引,簡單的整合2 。

Solutions 解決方案
Previouly I had described a much simpler way to previouly我所描述的更簡單的方式,去 integrate Tomcat 5.5 with Apache 2.x整合的Tomcat 5.5與Apache 2.x的 , in just 5 steps. ,在短短的5個步驟。

However we need to move further.不過,我們需要提出進一步。 We need to make Java Servlet container as easily integratable as php or ruby .我們需要使Java Servlet的容器很容易集成作為PHP中,或者紅寶石。 Running a separate Tomcat instance may not be an acceptable solution to many web hosting providers.運行一個單獨的Tomcat ,例如可能不是一個可以接受的解決辦法許多Web託管服務提供商。 We need to be able to run Tomcat within Apache itself, use its threads.我們需要能夠運行的Tomcat與Apache的本身,利用其線程。 In the distant past there was another Apache project JServ which did that.在遙遠的過去還有一個Apache項目jserv ,其中這樣做。 Later it was discontinued in favor of Tomcat.後來它被停止在贊成的Tomcat 。 Tomcat is powerful but most small developers do not need its full gamut of capabilities.雄貓是強大的,但大部分小型地產商並不需要充分的所有能力。 Most of them would be happy with a smaller subset which is available everywhere, even on one dollar hosting .他們大多會很樂意與一個較小的子集是無處不在,甚至在1美元兌主辦

And finally Sun and java community needs to approach web hosting providers and make the language ubiquitous in every hosting platform, big or small.最後, Sun和Java社區需要的做法,網站託管服務提供商,使語文無處不在每一個託管的平台,或大或小的。 Apachefriends has done an admirable job with XAMPP for LAMP community and has made Tomcat 5.5 available with its simplified LAMP installation. apachefriends已做了令人欽佩的工作與xampp燈社區,並已取得的Tomcat 5.5提供其簡化燈安裝。 Now if only we could package Java with all Linux and BSD installations by default…現在,只要我們能包的Java與所有Linux和BSD安裝默認情況下…