Re: Design patterns for Web services,
and work flows/composite se 2003-07-11 - By Andy Longshaw
Back
I'd be interested in any thoughts in this area too.
Patterns for Web Service composition per-se will
be generic, but as Web Services are the latest
"future of software" then as J2EE designers we
should know about them. There will also be
various J2EE-specific idioms for creating and
combining Web Services.
I have worked on one (long running) application
based on Web Services and am doing some work on
a second. As such, I can't really comment on
specific Web Service patterns as I can't meet the
"rule of three" yet :-) However, many of the familiar
patterns are very applicable inside Web Services
when working out their structure (Facade, Command,
etc.).
It strikes me that we will have similar debates around
Web Service use and patterns as we had around entity
beans in the early days. The key issue is the granularity
of the service and where it is appropriate to use
Web Services in any application design (i.e. don't just
use Web Service protocols everywhere and say you're
using Web Services - this is the Web Service equivalent
of calling fine-grained entity beans directly from the client...)
Cheers
Andy
At 10:52 11/07/2003 +1000, you wrote:
>Hi,
>
>Vijay suggested I send some questions to this list about patterns for Web
>Services implemented in J2EE...
>
>1 What's the current best practice for design patterns for Web Services
>(built on J2EE)
>
>2 What about work flows (which invoke Web Services)? Distributed
>execution of work flows?
>
>3 How about for Web Service Composition? (including perhaps some "OO"
>features such as inheritance, replication, reflection, etc?)
>
>I have an idea for distributed execution of workflows, where the work flow
>is deployed as a bunch of "control" Web Services - each controller service
>contains flow logic and invokes either other control services or
>eventually just "primitive" web services to do the tasks.
>
>Could you build/compose complex work flows and also management
>capabilities (e.g.) just by deploying the work flow as a bunch of proxy
>web services (and is there an obvious design pattern for proxy web
>services?) - some of which manage control/execution, others manage
>non-functional requirements (e.g. dynamic rebinding to find available
>services) etc. And do this recursively?
>Regards,
>
>Paul
>
>
>Paul Brebner
>Senior Software Research Engineer
>CSIRO Mathematical and Information Sciences
>Australian National University, Canberra, Australia
>+61 2 6216 7062
>
__ ____ ____ ____ ____ ____ ____ ____ ____ ____ ___
Andy Longshaw
Blue Skyline [ Consultancy, Writing, Training, Mentoring ]
email: andy@(protected)
phone: +44 (0)1625 611816
fax: +44 (0)1625 611816
"Wisdom, justice, compassion, integrity"
(The four words engraved on the mace of the Scottish
Parliament which seems to sum things up nicely)
====================================================================
Community Web Site (Core J2EE Patterns Catalog - Online Version):
http://java.sun.com/blueprints/corej2eepatterns
Getting Started (Beta Version):
http://developer.java.sun.com/developer/technicalArticles/J2EE/patterns/
Get the book:
http://www.amazon.com/exec/obidos/ASIN/0130648841/corej2eepatte-20 (See http://tte-20.ora-code.com)
List Archive:
http://archives.java.sun.com/archives/j2eepatterns-interest.html
Unsubscribing:
email "signoff J2EEPATTERNS-INTEREST" to listserv@(protected)
|
|
