File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes OO, Patterns, UML and Refactoring and the fly likes How Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » OO, Patterns, UML and Refactoring
Bookmark "How " Mashup Patterns" organized" Watch "How " Mashup Patterns" organized" New topic

How " Mashup Patterns" organized

Vijitha Kumara

Joined: Mar 24, 2008
Posts: 3902

Dear Author,

I Would like to know about how the book is organized. Is it more example oriented or more theoretical ? First chapter has used some HTML code and explained things nicely. What are the other kinds of examples used in the book (i.e: any other types of code and samples) ?

Thanks in advance,

[How to ask questions] [Twitter]
Mike Ogrinz

Joined: Apr 09, 2009
Posts: 17
Hi Vijitha,

The mashups are broken down into 5 major categories: Harvest, Manage, Enhance, Assemble, and Test. A complete description of the patterns is available at the book's companion website.

It is definitely example-oriented, as each of the 34 patterns covered has an average of 3 examples included. However, these examples are not code-based (see some of my other posts this week) owing to the current maturity level of the technology. The goal here is to get readers to break out of a traditional development mindset that makes them dismiss certain solutions as technologically impossible. All of the examples in the book can be created with current mashup tooling. The book gives ascribes a set of Core Activities to each of the patterns which will help you choose the right product to help implement the examples.

Michael Ogrinz
I agree. Here's the link:
subject: How " Mashup Patterns" organized
It's not a secret anymore!