axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nils Hammar (JIRA)" <>
Subject [jira] Commented: (AXIS-2150) Error calling web service after a re-deploy
Date Wed, 25 Jan 2006 14:38:09 GMT
    [ ] 

Nils Hammar commented on AXIS-2150:

The problem is still in Axis 1.3, and a study of the source code reveals the following:
In, the problem is likely caused by EngineConfigurationFactoryFinder.newFactory()
returning 'null', which ends up in EngineConfigurationFactoryFinder.newFactory(Object), and
that method seems to be "incomplete" according to the comments given.

As I see it it may be caused by the line services.nextResourceClass().loadClass(), which seems
to be throwing an Exception that in turn isn't handled at all, and the whole catch body is
just a comment. The Exception seems to be triggered by trying to load an already loaded class.
What's bad is that this condition should have been causing an exception instead of resulting
in a returned null pointer with no notification whatsoever.

> Error calling web service after a re-deploy
> -------------------------------------------
>          Key: AXIS-2150
>          URL:
>      Project: Apache Axis
>         Type: Bug
>     Versions: 1.2.1
>  Environment: Java sdk1.4.2_06
> JBoss 4.0.2 / TomCat 5.0 / WebSphere 6.0
>     Reporter: João Portela

> After a redeploy of an application (that called a web service), when I try to call a
web service the following error occurs: 
> ?Unable to locate a valid EngineConfigurationFactory?
> java.lang.NullPointerException
>         at org.apache.axis.client.Service.getEngineConfiguration(
>         at org.apache.axis.client.Service.getAxisClient(
>         at org.apache.axis.client.Service.(
>         at myapp.WebService1Soap_BindingStub.(Unknown Source)
>         ...
> Notes: 
>  - I have an axis configuration file in my ear/war application file.
> - It seems that after the redeploy it tries to use previous (load) configurations but
due to the redeploy, the configuration no longer exists.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message