Skip to main content

Local YUI combo loader

Quite a while ago I had users complaining they could not use my application from another secure network zone. It appeared the root cause was in using Yahoo CDN for serving YUI resources while there was no internet access in that specific network zone. Also living behind a proxy, our regular users used to suffer from longer delays from time to time due to proxying. An obvious solution turned out to be using a locally served YUI. For this a combo loader is required if you care about efficiency on Production.

To start with, there are several alternative open-source tools that can be used for combo loading:
The Node.js combo handler is supplied with rather self-contained README file at github. Nevertheless, I'll outline main steps here that worked for me:
  1. Install Node.js and npm package manager.
  2. Run npm install combohandler.
  3. Choose a location for the local YUI files, e.g. /opt/combohandler/yui.
  4. Download YUI3 release zip and YUI 2in3 release zip if needed.
  5. Place sources at the chosen location. Besides I've renamed the top directories, so I've got the following:
  6. ls /opt/combohandler/yui/
    2in3/  3.17.2/
    ls /opt/combohandler/yui/2in3/
    2.2.2/  2.3.1/  2.4.1/  2.5.2/  2.6.0/  2.7.0/  2.8.0/  2.8.0r4  2.8.1/  2.8.2/  2.8.2r1  2.9.0/  2.9.0pr1.2725/  build/  meta/
    ls /opt/combohandler/yui/3.17.2/
    align-plugin/  cssbase-context/  editor-para/  model-sync-rest/  series-marker/
    --- and many more here ---
  7. Create JSON routes config /opt/combohandler/yui/root.json:
  8. {
      "/yui/combo": "/opt/combohandler/yui"
  9. Start combohandler now: combohandler -p 8555 -b /yui/public -f /opt/combohandler/yui/root.json
Now it's time for some comments on the steps above. First, you can see I use both YUI3 and YUI 2in3 releases but I do not use YUI gallery modules though. If you need gallery modules as well, I hope you'll be able to make them working yourself although I'll give some useful links in the configuration section. Second, I've configured the port 8555 above and the base URL path /yui/public that is used for rewriting relative URLs. This base URL should provide direct access to any YUI resource. To give a better idea here is our Apache HTTP server virtual host configuration:
<VirtualHost *:80>
    Alias /yui/public "/opt/combohandler/yui"
    <Directory "/opt/combohandler/yui">
        Options None
        AllowOverride None
        Order allow,deny
        Allow from all
    ProxyPass /yui/combo http://localhost:8555/yui/combo
Finally the following should be working:

Application configuration
Configuring the application is much easier, you only need to fix yui.js location and provide a custom YUI config to enable local combo loader. Here is the javascript I've used:
YUI_config = {
  comboBase: '',
  combine:   true,
  groups: {
    yui2: {
      combine:   true,
      root:      '2in3/2.9.0/build/',
      patterns:  {
        "yui2-": {
          configFn: function (me) {
            if(/-skin|reset|fonts|grids|base/.test( {
              me.type = "css";
              me.path = me.path.replace(/\.js/, ".css");
              me.path = me.path.replace(/\/yui2-skin/, "/assets/skins/sam/yui2-skin");
You can see here a separate yui2 group configuration. If you are going to use YUI gallery modules, they can be configured using groups as well. For some examples you can refer to the related blog article and YUI forum topic.


Popular posts from this blog

DynamicReports and Spring MVC integration

This is a tutorial on how to exploit DynamicReports reporting library in an existing  Spring MVC based web application. It's a continuation to the previous post where DynamicReports has been chosen as the most appropriate solution to implement an export feature in a web application (for my specific use case). The complete code won't be provided here but only the essential code snippets together with usage remarks. Also I've widely used this tutorial that describes a similar problem for an alternative reporting library. So let's turn to the implementation description and start with a short plan of this how-to: Adding project dependencies. Implementing the Controller part of the MVC pattern. Modifying the View part of the MVC pattern. Modifying web.xml. Adding project dependencies I used to apply Maven Project Builder throughout my Java applications, thus the dependencies will be provided in the Maven format. Maven project pom.xml file: net.sourcefo

Do It Yourself Java Profiling

This article is a free translation of the Russian one that is a transcript of the Russian video lecture done by Roman Elizarov at the Application Developer Days 2011 conference. The lecturer talked about profiling of Java applications without any standalone tools. Instead, it's suggested to use internal JVM features (i.e. threaddumps, java agents, bytecode manipulation) to implement profiling quickly and efficiently. Moreover, it can be applied on Production environments with minimal overhead. This concept is called DIY or "Do It Yourself". Below the lecture's text and slides begin. Today I'm giving a lecture "Do It Yourself Java Profiling". It's based on the real life experience that was gained during more than 10 years of developing high-loaded finance applications that work with huge amounts of data, millions currency rate changes per second and thousands of online users. As a result, we have to deal with profiling. Application pro

Using Oracle impdp utility to reload database

Here I'll show an example of using Oracle Data Pump Import (impdp) utility. It allows importing Oracle data dumps. Specifically, below is the list of steps I used on an existing Oracle schema to reload the data from a dump. Steps to reload the data from an Oracle dump We start with logging into SQL Plus as sysdba to be able to manage users. sqlplus sys/password@test as sysdba Dropping the existing user. CASCADE clause will ensure that all schema objects are removed before the user. SQL> DROP USER test CASCADE; Creating a fresh user will automatically create an empty schema with the same name. SQL> CREATE USER test IDENTIFIED BY "testpassword"; Granting DBA role to the user to load the dump later. Actually, it's an overkill and loading the dump can be permitted using a more granular role IMP_FULL_DATABASE . SQL> GRANT DBA TO test; Registering the directory where the dump is located. SQL> CREATE DIRECTORY dump_dir AS '/home/test/dumpd