• 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 ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin

thoughts - Does top-down web service approach mar OO concepts of polymorphism and inheritance

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

For my new project we are using top-down approach to web service development and as we go about creating xml schemas and wsdl operations increasingly I feel OO concepts of polymorphism and inheritance will not fit in naturally. This is related to the inputs to wsdl operations. All inputs now don't extend any domain class. I am not sure there is a way to do it nor is that my question.
So as I go about creating/customizing the java code produced by the wsdl2java converter I see it difficult to fit the OO concepts and relying more on compose-always design paradigm.

Is this fine and good sign and also is it a generally preferred behavior with top-down implementation.

Let me know your thoughts

Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic