Skip to main content

Aggregating DWR interface scripts

My company has a website and running Yslow on it reported that the no of HTTP requests were in the range of 120-130. Accessing the site from UK was pretty slow. Now we used CSS sprites to reduce the no of css images and we were already using JS and CSS aggregation. There were still 10-12 DWR interface scripts and as browser stops rendering while its downloading and rendering js files. I was looking for a solution for aggregate DWR generated interfaces. I searched a lot and than landed onto JAWR. As we are using build time aggregation for static JS I am using JAWR only for generated interface JS. Here are the things I did.

Add jawr lib to WEB-INF/classes
==============================web.xml============================
    <servlet>
        <servlet-name>JawrServlet</servlet-name>
        <servlet-class>net.jawr.web.servlet.JawrServlet</servlet-class>
        <init-param>
            <param-name>configLocation</param-name>
            <param-value>/jawr.properties</param-value>
        </init-param>
        <init-param>
            <param-name>mapping</param-name>
            <param-value>/jawrBundle/</param-value>
        </init-param>
        <load-on-startup>2</load-on-startup>
    </servlet>
    <servlet-mapping>
        <servlet-name>JawrServlet</servlet-name>
        <url-pattern>/jawrBundle/*</url-pattern>
    </servlet-mapping>   

Note JAWR servlet should start after DWR servlet   
=====================jawr.properties===============================

# Common properties
jawr.debug.on=false
jawr.gzip.on=true
jawr.gzip.ie6.on=false
jawr.charset.name=UTF-8
jawr.js.bundle.agg_dwr.id=/jawrBundle/agg_dwr.js
jawr.js.bundle.agg_dwr.mappings=dwr:_**
#dont forget the below property.
#I forgot it and struggled for 6 hours after reading JAWR code to figure this out
jawr.dwr.mapping=/dwr/
======================JSP changes==============================
<%@ taglib prefix="jwr" uri="http://jawr.net/tags" %>
<jwr:script src="/jawrBundle/agg_dwr.js"/>
====================================================
Labels:

Comments

  1. thymianDecember 9, 2009 at 9:19 AM

    This aggregation module exhibit effective Java programmers how to impact with DWR to create coercive AJAX applications. It starts with a tutorial on DWR’s important features and functions. Then it covers surround up the utilization environment.

    ReplyDelete

Post a Comment

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are Download Erlang Download Rabbit MQ Server Download Rabbit MQ Java client jars Compile and run the below two class and you are done. This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time. For more information on AMQP, Exchanges, Queues, read this excellent tutorial http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/ +++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++ import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.se...
23 comments
Read more

Spring 3.2 quartz 2.1 Jobs added with no trigger must be durable.

I am trying to enable HA on nodes and in that process I found that in a two test node setup a job that has a frequency of 10 sec was running into deadlock. So I tried upgrading from Quartz 1.8 to 2.1 by following the migration guide but I ran into an exception that says "Jobs added with no trigger must be durable.". After looking into spring and Quartz code I figured out that now Quartz is more strict and earlier the scheduler.addJob had a replace parameter which if passed to true would skip the durable check, in latest quartz this is fixed but spring hasnt caught up to this. So what do you do, well I jsut inherited the factory and set durability to true and use that public class DurableJobDetailFactoryBean extends JobDetailFactoryBean {     public DurableJobDetailFactoryBean() {         setDurability(true);     } } and used this instead of JobDetailFactoryBean in the spring bean definition     <bean i...
7 comments
Read more

Killing a particular Tomcat thread

Update: This JSP does not work on a thread that is inside some native code.  On many occasions I had a thread stuck in JNI code and it wont work. Also in some cases thread.stop can cause jvm to hang. According to javadocs " This method is inherently unsafe. Stopping a thread with Thread.stop causes it to unlock all of the monitors that it has locked". I have used it only in some rare occasions where I wanted to avoid a system shutdown and in some cases we ended up doing system shutdown as jvm was hung so I had a 70-80% success with it.   -------------------------------------------------------------------------------------------------------------------------- We had an interesting requirement. A tomcat thread that was spawned from an ExecutorService ThreadPool had gone Rogue and was causing lots of disk churning issues. We cant bring down the production server as that would involve downtime. Killing this thread was harmless but how to kill i...
6 comments
Read more