Saturday, May 22, 2010

OSB, Eclipse and Axis2

If you plan to use Axis2 as a runtime for Web Services clients, remember that you should download axis2-1.4.1, and not the latest release, otherwise you will get :


java.lang.NoClassDefFoundError: org/apache/http/HttpResponseFactory
    at org.apache.axis2.transport.http.SimpleHTTPServer.init(SimpleHTTPServer.java:116)
    at org.apache.axis2.engine.ListenerManager.init(ListenerManager.java:74)
    at org.apache.axis2.context.ConfigurationContext.getListenerManager(ConfigurationContext.java:692)
    at org.apache.axis2.client.ServiceClient.configureServiceClient(ServiceClient.java:163)
    at org.apache.axis2.client.ServiceClient.(ServiceClient.java:143)


All this is very sad. There is never a bloody compatibility check in Java classes and Jars... all the time you must discover which version goes with which by trial and error, exceptions and painful googling for explanations.... I would expect in 2010 a mature language like Java would enforce a standardization on library compatibility...

2 comments:

Br1207yantScipio1 said...

Cast not the first stone. .............................................

Pierluigi Vernetto said...

well, either Java will address this kind of issues and soon, or it will keep losing market share and Java programmers will have to learn how to milk cows. As simple as that. Companies cannot afford paying developers to waste days troubleshooting classpath and library issues. Libraries should be plug-verify-and-play. I do not settle for anything less than perfect.