Skip to main content

路 3 min read

HTTP compression has improved a lot the download time of content from servers. In the context of Web Service it could be very interesting to also use HTTP compression to improve the network traffic. Firs, I am explaining how to compress a SOAP response when you have a Web Service running in Oracle Containers for J2EE (OC4J) using a generic servlet filter. I have to give credit to since he has created the Filter and documented how to do such thing using Axis.聽

So you can take a look to the following article for more details, you can read the 2 following article, or jump to the next paragraph that explains how to configure your JAX-RPC based service to send compressed HTTP response.

In this sample I am showing how to compress the SOAP response using a servlet filter, it is also possible to use some other Oracle infrastructure element to achieve that such as Oracle HTTP Server/Apache, or Oracle Webcache.

1- Install the compression filter library in your application#

Download the compression filter library 2wayfilter-1.2.jar and copy it into the Web application's WEB-INF/lib folder

2- Configure your application to use the filter#

The configuration of a servlet filter is done using the web.xml where you reference which servlet or URL will be using the filter. As you may knowin JAX-RPC, the HTTP endpoint of a service are exposed as servlet and defined in the web.xml. You can choose to compress all the endpoint/URL or create a new servlet mapping, that will become a new SOAP endpoint and only compress this one. If you take the option of creating a new endpoint keep in mind that it will not be added to the WSDL automatically, so the client application will have to point explicitly to the compressed endpoint URL to take benefits of it.

<web-app xmlns="" xmlns:xsi=""  xsi:schemaLocation=""  version="2.4">  <servlet>    <description>Web Service CustomerServiceSoapHttpPort</description>    <display-name>Web Service CustomerServiceSoapHttpPort</display-name>    <servlet-name>CustomerServiceSoapHttpPort</servlet-name>    <servlet-class></servlet-class>    <load-on-startup>1</load-on-startup>  </servlet>  <servlet-mapping>    <servlet-name>CustomerServiceSoapHttpPort</servlet-name>    <url-pattern>CustomerServiceSoapHttpPort</url-pattern>  </servlet-mapping>
  <!-- New servlet mapping to handle compressed SOAP Messages -->  <servlet-mapping>    <servlet-name>CustomerServiceSoapHttpPort</servlet-name>    <url-pattern>CompressedCustomerServiceSoapHttpPort</url-pattern>  </servlet-mapping>

  <!-- Filter definition with mapping on the compressed endpoint -->  <filter>    <filter-name>2WayFilter</filter-name>    <filter-class>com.osmoticweb.gzipfilter.GZIP2WayFilter</filter-class>  </filter>  <filter-mapping>    <filter-name>2WayFilter</filter-name>    <url-pattern>CompressedCustomerServiceSoapHttpPort</url-pattern>  </filter-mapping>

You can now package and deploy your application.

3- Create & Invoke the service#

In this basic configuration you have only changed the servlet that is the HTTP endpoint of your service. So the compressed endpoint is not present in the WSDL, but you can use any of the URL to create your proxy.

When you have created your proxy, if you want to access the endpoint that will return the compressed response you must be sure that you are calling the correct endpoint. You can set the endpoint using the setEndpoint method, of your Web Service client.

This is it!

I will in a next post explain how you can using the Oracle Web Service client API send a compressed request that will have to be uncompressed on the server using the same filter.

路 One min read

Groovy release 1.0 is here now !

You can find the release at the following location:

Congratulations to all the Groovy developers, and users that have done a great job with this language that is here in production. And it is interesting to see that more and more projects are using Groovy as part of their infrastructure to simplify development:

  • XWiki
  • Spring 2 integration
  • Grails
  • ... and many development teams in custom projects

So once again happy new year to all... and enjoy it with Groovy !

路 One min read

As Mac user I sometimes need to use Windows (too often...) or Linux computer, and for this I have been using either my PC or Parallels. Parallels is great but in my daily job my coworker are mainly using VMWare images....

VMWare has now open the VMware Virtualization for Mac Beta Program. If you like me need virtualization jump on it and give feedback...

路 One min read

The groovy project gets funding for its development. Big Sky is hiring Jochen Theodorou one of the Groovy commiter. For the people that do not know Big Sky. Big Sky is the company behind the the No Fluff Just Stuff symposium tour. Talking about this symposium, in 2007, Groovy and Grails will have a dedicated track.

More about this funding:

In addition to this very good news, here some other activities around Groovy and Grails:

  • Releases of Groovy 1.0 and Grails 0.4
  • Two books on Groovy and one on Grails.
  • A dedicated Groovy and Grails website:
  • Also a dedicated Groovy and Grails conference: theGrails eXchange 2007
  • And the third Groovy Developer Conference in Paris at the end of January

路 One min read

路 One min read

The London Groovy and Grails User Group will be holding their next meeting on Wednesday, 6th December 2006 at Skills Matter in London and for the first time ever the meeting will be available via a live web conference, so don't worry if you are not in London!

Speaking at this month's meeting will be Graeme Rocher, Grails Project Lead and CTO at Skills Matter. During his talk entitled; Grails Dynamic Tags: Making Tag Libraries Agile, Graeme will discuss Groovy Server Pages and its support for the creation of dynamic tag libraries without the need for configuration.

John Wilson, Groovy Committer, will also be presenting at this meeting. During his talk, entitled; The MetaClass: How Groovy works Under the Hood, John will shed light on the MetaClass so you can better understand its' function and see how to use it to get your Groovy programs smaller, clearer and faster.

For more information on attending this meeting or signing up for the web conference, please go to:

路 One min read

WS-Security provides a way to protect Web Services at the message level (SOAP) and it is independent of the protocol used (HTTP, JMS, ...). However, some services are still using HTTP based authentication for protection. JAX-RPC and its Oracle implementation provides a way to set the username and password in the client (Stub) using some properties on the Stub.

((Stub)port)._setProperty(Stub.USERNAME_PROPERTY, "username");((Stub)port)._setProperty(Stub.PASSWORD_PROPERTY, "password");  

That's it...

Theses properties are shortcuts to the standard JAX-RPC properties:

This code is the same when you are using the Call interface.