• 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:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

trying to get a contract-last SOAP-based web service running - on the 2 yard line

 
Ranch Hand
Posts: 141
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Java 1.7
Spring 3.1.1 with Spring-WS 2.1.1
Joda
Hibernate 3.6
SqlServer 2008 R2
Maven 3
Tomcat 7
Eclipse 3.7

...and the saga continues...

have made progress with my contract-last SOAP web service.
Project's name in Eclipse is :
dept_forms_webservice
And after fighting the lifecycle-mapping demon it now compiles and generates FormsService.wsdl in
.../META-INF/schema

I've simplified a few things...

com.xxx.forms.web.endpoint.FormsEndpoint.java


com.xxx.forms.web.endpoint.FormsEndpointImpl.java


webapp/WEB-INF/web.xml


webapp/WEB-INF/spring/root-context.xml


webapp/WEB-INF/spring/appServlet/servlet-context.xml


and all this generates
.../META-INF/schema/FormsService.wsdl


Tomcat manager shows the web service dept_forms_webservice as running
but clicking on the service threw the dreaded "no bean named 'cxf' is defined" error.
Googling turned up only one useful suggestion - moving the cxf imports from servlet-context to root-context.
Sure enough that solved that particular problem.

But color me blind but I still can't seem to bring up the wsdl in my browser.
Clicking on the service within Tomcat manager now reports "No service was found".
Shouldn't it list the service(s) available?

And trying anything starting with
http://localhost:8080/dept_forms_webservice
also reports "No service was found"

trying anything starting with
http://localhost:8080/endpoint.web.forms.xxx.com
throws a 404

So at this point I'm utterly stumped. There must be some fiendishly subtle configuration
error I'm making.

Could use a little more help please.


TIA,

Still-struggling Steve

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


[1] The qddress attribute looks wrong. Should it not be /FormsEndpointPort or about, should it?
[2] After that, your trys should follow closely what the soap:address tells you what to do. And that your port exposing the services is 9090 as shown there, or is it a typo?
Test again focusing on these details?...
reply
    Bookmark Topic Watch Topic
  • New Topic