- This topic has 3 replies, 3 voices, and was last updated 15 years, 9 months ago by
.
-
Posts
-
Hello,
When I Debug-As, and select GlassFish, and run my web service, the server is starting with old wsdl configurations. The internal Web Service Explorer runs fine, but MyEclipse won’t push changes to the WSDL seen by the app server.
Any ideas? We’re using MyEclipse 7.0 and Sun App Server 9.1 (glassfish) .
Thanks.
-TomTom,
I have asked the dev team to look into this issue and they will get back to you with a reply asap.Tom,
When you say the internal WS Explorer works find, what WSDL is it accessing? Do you use a file system based URI or a reference to the WSDL file in your running application?
If the WS Explorer works fine, that indicates that your changes are indeed deployed to the server, or I’d think you should be seeing a lot of issues with missing operations, mismatched parameters etc.
Could you elaborate further? What do you do to force the new changes to the app server right now?
Brian,
The WSDL is being accessed from “platform:/resource/…/ServiceX.wsdl when I test the WS from the Web Service Explorer.
To force a change to the WSDL on the Sun App Server, I shut down the app server from within MyEclipse, then I “asadmin.bat start-domain domain1” from the command line, then undeploy the ws from the Admin interface. Then shut-down the App Server (asadmin stop-domain), then try Debug-As again.
The thing I changed originally, which precipitated this problem, was the @WebMethod used as the entrypoint. The WS wizard gave this a ServiceXDelegate name. I changed the name in all the right places, including the WSDL from ServiceXDelegate to ServiceXFoo . Only after violently reploying the app (described above) did everything work as expected in the Sun App Server.
