• 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

Web-Service Hello World Problem For Newbie

 
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Everyone,

I'm a newbie to Web-Services and have been following this tutorial point-to-point http://24bytes.com/helloworlds/WebService/hellowebservice.html.

Essentially all the code I wrote is the following:



I let Eclipse's Generate Web Service automator do the rest. But it seems its not deploying to my Tomcat correctly at all! It's publishing just fine to Tomcat but when I goto my configured address
http://localhost:9080/HelloWorldWebService/ - which is what I think the auto-generated WSDL was pointing to - it kept saying 404 - File Not Found.

Now the tutorial in the link wasn't clear how the web-service address was configured, but I assumed that whatever the Web Service automator spit-out as the WSDL - should have it correctly configured once the WAR was pushed to Tomcat...

I know this is a rookie-mistake, but what am I doing wrong?
 
Perry Terrance
Ranch Hand
Posts: 71
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Well I figured it out myself!

Apparently in the targetNamespace generated by the automator was something really stupid like: http://helloworld/. I had to manually edit it to localhost, and now it works.

So apparently (if I am understanding this right) - I have to manually make sure the Namespace of my deployed EAR matches correctly whatever http://yada/yada that the Web-Service was ultimately be on - so if the EAR is in a http://localhost/myFirstProject/, then I have to make sure my webservice namespace is targetted to that... Rookie-Mistake indeed...
 
Villains always have antidotes. They're funny that way. Here's an antidote disguised as a tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic