aspose file tools*
The moose likes Web Services and the fly likes Book Promo: Favored Web Service Design Approach? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Java 8 in Action this week in the Java 8 forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "Book Promo: Favored Web Service Design Approach?" Watch "Book Promo: Favored Web Service Design Approach?" New topic
Author

Book Promo: Favored Web Service Design Approach?

Peer Reynders
Bartender

Joined: Aug 19, 2005
Posts: 2906
Does your book SOA Using Java� Web Services (Sample Chapter: Basic SOA Using REST, amazon US) drive home the fact that web services are in fact XML document exchange systems, not
  • yet another remote procedure call (RPC) technology or
  • an object serialization protocol to beam arbitrary object graphs over the internet

  • despite the various vendor tool offerings of �web service magic pixie dust� (Ted Neward�s words)?

    Does it give preference to the document-oriented and contract (WSDL) first approach ?
    [ May 29, 2007: Message edited by: Peer Reynders ]

    "Don't succumb to the false authority of a tool or model. There is no substitute for thinking."
    Andy Hunt, Pragmatic Thinking & Learning: Refactor Your Wetware p.41
    Mark D. Hansen
    author
    Ranch Hand

    Joined: May 29, 2007
    Posts: 61
    Hi Peer,

    Good questions. I share Ted Neward's views on the issue of "magic pixie dust" In fact, Ted wrote the Foreward to my book. FYI, there is a transcript of Ted's interview on that topic here -> http://www.theserverside.com/news/thread.tss?thread_id=39757#205460

    My book does focus on the document-oriented approach to Web services. All of the WSDL examples use the document/literal style. Chapter 4 contains a detailed description of both the rpc-oriented and the document-oriented approaches, and explains why document-oriented is preferable in most situations.

    One difficulty here is that JAX-WS and JSR-181 do give you plenty of "magic pixie dust" that lets you create Web services from Java by simply adding the @WebService annotation to your code.

    My book explains why that is not usually a very good idea, and explains how and why programmers should use the "Start from WSDL" approach to SOA and Web Services.

    I've found that it is a fine line, however. Programmers need to be practical and meet deadlines. So, the book shows them how to use the tools that are available (including the "magic pixie dust"), but also encourages good SOA design principles.

    -- Mark


    Mark D. Hansen
    Founder and President, AgileIT LLC http://agileitinc.com/
    Author of "SOA Using Java Web Services" - http://soabook.com/
    David Bueche
    Greenhorn

    Joined: Oct 08, 2004
    Posts: 4
    Mark,

    In the area of "pixie dust", do you discuss in your book any JAX-WS approach for generating a WSDL from Java classes, then generate the Web Service from that (or even a single-step approach that does both of these)?

    Also, do you do any comparisons between JAX-WS and Apache Muse regarding pros and cons for writing WS-Notification services?

    Thanks,
    -David
     
    I agree. Here's the link: http://aspose.com/file-tools
     
    subject: Book Promo: Favored Web Service Design Approach?
     
    Similar Threads
    Book Promo: Value of REST web services in the �real world�?
    Mark Hansen: Welcome
    More up to date and better than "Building Web Services with Java:" book?
    Book Promo: Java SOA without Java EE 5?
    J2EE Webservices