Deploying Existing Web App With New JWS

Question

Hi all,
I've been banging my head against a brick wall for a few days on this, but I'm sure it must be something trivial. Hopefully someone here will have some advice...
In a nutshell, I'm working on an existing web application, running on Weblogic 8.1, in a clustered environment. I've added a new JWS web service which is largely standalone, but it uses controls from elsewhere in the application.
Locally, on my development box, it works perfectly - I can run it from Weblogic Workshop, and see the handy test form to run the web service, as well as seeing the WSDL by pointing my browser at http://localhost:7001/app/path/Service.jws?WSDL
However, I've now built the EAR for the whole application, and deployed it to our test environment (clustered - a mirror (hopefully!) of the production environment).
When I go to http://test-box:7002/app/path/Service.jws?WSDL I see a nasty-looking error page that looks like:
WebService ERROR
Error:
null
Stack Trace:
null
When I try the same URL without the ?WSDL on the end (so just http://test-box:7002/app/path/Service.jws), I see the nice Weblogic Web Service page, showing that it knows there's something there, but it has no content, just the 'Overview' tab, followed by:
Public Information
about Service.jws Web Service
and that's it - locally I see the same thing, but with options for viewing the WSDL and testing the service.
I'm confident that the URL is correct, because if I put rubbish in, I get a different error message.
Reading around, I've found lots of resources for 'how to deploy a web service to a production environment' for Weblogic 7, but much less for 8.1. I've seen references to jwsCompile, for example, which I think is specific to 7, because I can't find any references to it in the 8.1 docs, but perhaps that's wrong?
I'm pretty sure there's a configuration setting I'm missing, or a step in the deployment, but I'm stuck as to what it is!
Any advice gratefully received.
Edit: I should have mentioned that there are two other JWS's in the same app, both of which have the same symptoms as my new one (they've been there for a while, but are unused).

Answer 1

My gut reaction is that there might be an issue with the frontend settings not set up correctly, see 9.2 docs in lieu of 8.1 docs:
http://edocs.bea.com/wls/docs92/webserv/setenv.html#wp220521
You should also open a support case as they could probably identify your issue quickly.