• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

org.apache.axis.ConfigurationException

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
when i call web serivce,the following error occurs:

org.apache.axis.ConfigurationException: org.apache.axis.ConfigurationException: No engine configuration file - aborting!

I don't konw how to fix this problem, it occurs this error when i call web service. is it happened in the jar file because i export web serivce source code to jar file.



anyone help~




 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
When debugging web service app errors I feel the first thing to determine is where the error occurred.

1. In your client during creation of the request but before the request is even sent.
2. Client side used bad URL so request never got to server.
3. Server side - request got to server but no service matching the request is found (could even result in a HTML formatted error page)
4. Server side - request got to the right service but it could not be executed
5. Back on client side - client gets response but does not handle it correctly.

And thats why debugging web services is not trivial. Utilities such as SOAPui can help you figure things out.

Bill
 
Joyce Leung
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

William Brogden wrote:When debugging web service app errors I feel the first thing to determine is where the error occurred.

1. In your client during creation of the request but before the request is even sent.
2. Client side used bad URL so request never got to server.
3. Server side - request got to server but no service matching the request is found (could even result in a HTML formatted error page)
4. Server side - request got to the right service but it could not be executed
5. Back on client side - client gets response but does not handle it correctly.

And thats why debugging web services is not trivial. Utilities such as SOAPui can help you figure things out.

Bill



thanks so much, the problem is solved.
reply
    Bookmark Topic Watch Topic
  • New Topic