Okay, I removed the server-config.wsdd from my project so it wouldn't auto-deploy on startup. I then deployed it manually from the commandline and it worked perfected. The contents of the 'service' tag from the config file were copied directly into the deploy.wsdd. So, if I try to have it deployed on startup (via server config file) it sort of gets deployed - you can check it via services/name but if you attempt services/name?wsdl you get a 404 and attempting to call the service from a client results in a weird target service null soap fault.
Is this a bug or did I miss the boat?
Ryan Cuprak
[EMAIL PROTECTED]
Office: (203)-786-5682
Cell: (203)-376-8789
| Ryan D. Cuprak/507107/EKC@Kodak
02/19/2003 03:29 PM
|
To: [EMAIL PROTECTED] cc: Subject: Re: Determining if a service is deployed (wrapped in my own webapp) |
I am using axis 1-1 Release candidate 1 - downloaded it yesterday from the Axis website. If I type in a service that obviously isn't there (instead of GMP), I receive a 404 error page.
The only weird thing I am doing is deploying my webservice with 'server-config.wsdd' so it is immediately available.
Ryan Cuprak
[EMAIL PROTECTED]
Office: (203)-786-5682
Cell: (203)-376-8789
| "Steve Loughran" <[EMAIL PROTECTED]>
02/19/2003 03:17 PM | To: <[EMAIL PROTECTED]> cc: Subject: Re: Determining if a service is deployed (wrapped in my own webapp) |
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 19, 2003 12:13
Subject: Re: Determining if a service is deployed (wrapped in my own webapp)
> Thanks,
> I tried http://149.98.242.166:8080/GMPServer/services/GMP?WSDL
> but recieved a http 404 code.
if you get a 404, then there is no service registered there.
in axis1.0, the 'hi there' message wasnt smart enough to tell if there
really was a service there, but in 1,1 it is. Maybe you are still running
Axis1.0, no?
