Modularized JavaScript with JBoss Portal Platform 6 – Avoid Conflicts, Promote Re-usability

http://howtojboss.com/2013/02/05/modularized-javascript-with-jboss-portal-platform-6-avoid-conflicts-promote-re-usability/

JBoss Portal Platform 6

JBoss Portal Platform 6 Beta is now available.
http://www.redhat.com/promo/jpp6/

Many new features are documented there:

• Built on blazingly fast, lightweight JBoss Enterprise Application Platform 6 technology
• Develop with JSF2 and Rich Faces 4 in portlets, via Portlet Bridge
• Implement single sign-on (SSO) using SAML 2.0
• Launch fast with Maven quick starts

Portlet and JavaScript

However, to developers and architects, one of the first issues and most difficult issue we face in any portal implementation is – what are the best practices to use JavaScripts in a portal platform?

Imagine if you have 2 portlets both using a shared JavaScript, such as jQuery – how would you share the JavaScript between the 2 portlets?

• Each Portlet include its own
  • This is largely a no-no.  If each portlet include its own jQuery in a <script> tag, they’ll most likely run into conflicts or unnecessarily reload a script already loaded.
• Deploy a single version
  • Then what if you need multiple versions?
  • What if some portlets needs a different version of the JavaScript library?

Now, expand this dilemma to not just common JavaScripts libraries, but to all of your application’s JavaScripts!

Oh, and don’t forget, you may also want to minify and combine scripts to reduce latency, to be Content Delivery Network (CDN) friendly, and ultimately, to improve your customer’s browsing  experience.

Node.js란 무엇인가? - http://blog.outsider.ne.kr/480

'장고(Django)'로 쉽고 빠른 웹 개발 - http://biohackers.net/wiki/RapidWebDevelopmentByDjango

Play Framework - http://www.playframework.org/documentation/2.0.1/Home

 : Play는 Java코드에서 변경된 사항이 서버 재시작없이 바로 반영된다.

   이는 Play가 컴파일된 class 파일이 아닌 Java소스코드를 직접 읽기 때문에 가능하다. 

   Play는 자체 컨테이너를 내장하고 있는데 현재 Play가 사용하는 컨테이너는 JBossNetty다.

   이전에 아파치 Mini를 사용하다가 WebSocket을 지원하기 위해 변경했다.

   그렇다고 Play로 개발된 웹 애플리케이션을 자체 서버에서만 실행할 수 있는 것은 아니다.

   Tmocat과 같은 일반 서블릿 컨테이너에서도 얼마든지 실행 할 수 있다. 

   * Source code on github : https://github.com/playframework