 | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Struts - A MVC web framework | | Tomcat - JSP/Servlet container | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | | JSP - A mailing list about Java Server Pages specification and reference | |
Struts & Hibernate
|
|
|
| | Design patterns for Web services,
and work flows/composite servic | Design patterns for Web services,
and work flows/composite servic 2003-07-10 - By Paul Brebner
Back
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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 6.00.2800.1126" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial
size=2>Hi,</FONT></SPAN></DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><FONT face=Arial><FONT size=2><SPAN class=353161800-11072003>Vijay
suggested I send some questions to <SPAN class=717294900-11072003>this list
about patterns for Web Services implemented in
J2EE...</SPAN></SPAN></FONT></FONT></DIV>
<DIV dir=ltr><FONT face=Arial><FONT size=2><SPAN class=353161800-11072003><SPAN
class=717294900-11072003></SPAN></SPAN></FONT></FONT> </DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial><FONT size=2><SPAN
class=717294900-11072003>1 </SPAN>What's the current best practice for design
patterns for Web Services (<SPAN class=717294900-11072003>built on
</SPAN>J2EE)</FONT></FONT></SPAN></DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial><FONT size=2><SPAN
class=717294900-11072003>2 </SPAN>What about work flows (which invoke Web
Services)? Distributed execution of work flows?</FONT></FONT></SPAN></DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><SPAN class=717294900-11072003><FONT
face=Arial size=2></FONT></SPAN></SPAN> </DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><SPAN class=717294900-11072003><FONT
face=Arial size=2>3 How about for Web Service Composition? (including perhaps
some "OO" features such as inheritance, replication, reflection,
etc?)</FONT></SPAN></DIV>
<P dir=ltr><FONT face=Arial><FONT size=2>I have an idea for distributed
execution of workflows,<SPAN class=353161800-11072003> 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. </SPAN></FONT></FONT></P>
<P dir=ltr><SPAN class=353161800-11072003><FONT face=Arial><FONT size=2>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.<SPAN class=717294900-11072003>
And do this recursively?</SPAN></FONT></FONT></SPAN></SPAN></P>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial
size=2>Regards,</FONT></SPAN></DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV dir=ltr><SPAN class=353161800-11072003><FONT face=Arial
size=2>Paul</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/rtf format -->
<P align=left><SPAN lang=en-au><B><FONT face=Arial size=2>Paul
Brebner</FONT></B></SPAN> <BR><SPAN lang=en-au><I><FONT face=Arial size=2>Senior
Software Research Engineer</FONT></I></SPAN> <BR><SPAN lang=en-au><FONT
face=Arial color=#0000ff size=2>CSIRO Mathematical and Information
Sciences</FONT></SPAN> <BR><SPAN lang=en-au><FONT face=Arial size=2>Australian
National University, Canberra, Australia</FONT></SPAN> <BR><SPAN
lang=en-au><FONT face=Arial size=2>+61 2 6216 7062</FONT></SPAN> </P>
<DIV> </DIV></BODY></HTML>
|
|
|
