axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernier (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-2150) Error calling web service after a re-deploy
Date Wed, 01 Mar 2006 10:39:42 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2150?page=comments#action_12368255 ] 

Bernier commented on AXIS-2150:
-------------------------------

Hi,
I'm working on a Portal project with some webservices integrations on Sun One Web servers
and App servers and I also face this issue.
I confirm that Axis 1.3 don't solve the issue.
I'm planning to find a solution for this, and for me there are only three ways :
     * having a patch from axis. But When ? will this issue taken in account for the next
Axis version ?
     * finding a solution to make the Axis librairys work ....
     * going on Sun Webservices librairys but this will be painfull 

Can you tell me what I can do, do you have a solution to make this work or should I wait 
for a patch  ?

Thank you for your answers,


> Error calling web service after a re-deploy
> -------------------------------------------
>
>          Key: AXIS-2150
>          URL: http://issues.apache.org/jira/browse/AXIS-2150
>      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(Service.java:812)
>         at org.apache.axis.client.Service.getAxisClient(Service.java:103)
>         at org.apache.axis.client.Service.(Service.java:112)
>         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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message