ALSB - Java Callout (.jar using commons-httpclient-3.1)

Question

Hello everyone,
I'm having a not so funny problem.
I made a Java class, that will be called by a Proxy Service (Java callout). I'm using the commons.httpclient-3.1.jar (+ codec and logging).
Here's the code:
package util.http;
import org.apache.commons.httpclient.HttpClient;
import org.apache.commons.httpclient.methods.*;
public class UtilitaireHTTP {
// method used by the Proxy Service
public static String getLastModified (String url){
return getHeader(url,"last-modified");
private static String getHeader(String url, String header){
HttpClient client = new HttpClient();
String lastModified = "404";
HeadMethod head = new HeadMethod(url);
try {
//not working
/*int statusCode = client.executeMethod( head );
if (statusCode == 200){
     lastModified = head.getResponseHeader(header).getValue();
//working
lastModified = "200";
catch(Exception e){
     System.out.println(e);
finally {
// release any connection resources used by the method
head.releaseConnection();
return lastModified;     
Here's the problem: Whenever I remove the comment block, test it (it's going to work with JUnit), create a JAR. Import it into ALSB jar resources folder. When I do a Java Callout in a Proxy Service I won't be able to see my method getLastModified. If I put that block in comment, re-do all the export import, I'll see the method in the list.
//not working
/*int statusCode = client.executeMethod( head );
if (statusCode == 200){
     lastModified = head.getResponseHeader(header).getValue();
//working
lastModified = "200";
Anyone knows the solution or problem.
Thank you!
Van

Answer 1

While playing with java callouts i've built working "groovy callout" sample. This way you can keep logic in your alsb proxy service rather than in jar file. Have a look. http://blog.aujava.com/?p=64