« Weblog opened... | Main | Apache Axis Installation »
March 1, 2006
Master thesis, day 1
I started writing my master thesis today.
The topic is "Concepts for loose coupling in service-oriented architectures with special web services / XML proxy modifications". I did some research and I think this is a very interesting topic.
Short summary of planned content:
- What are web services, technologies used, connection to Java (JAX-RPC)
- What is loose coupling, description using table from (Carlos Perez: Principles of Loosely Coupled APIs).
- Why JAX-RPC is not really loosely coupled (unusable stubs if interfaces are changed) and what to use else (conversational style)
- How to use conversational style and how to make it more easy to use this way
- Two main concepts:
- Being able to check XPath expressions at compile time (use XPath to access specific SOAP nodes)
- Being able to be more flexible which methods and attributes to expose/to use using Java 5 annotations
Posted by Dominik Marks at March 1, 2006 9:04 AM
Comments
"Conversational style" is something different -- that would be when consecutive calls can rely on some conversational state that has been established. For example, a login, required by some interactions, followed by a logoff, could form a conversation.
The contrast to stubs/skeletons/proxies would be document-oriented or message-oriented -- the message exchanged, or its content, become first class citizens in the programming model.
Posted by: Stefan Tilkov at March 1, 2006 10:35 PM
This is what I learned at my lectures at the university of science.
There were two message exchange concepts, one was called RPC-style and the other one was called Conversational style.
I will use the term "document-oriented style" in my thesis, this does not matter.
Posted by: Dominik Marks at March 2, 2006 12:56 PM
In the "SOAP Version 1.2 Part 0: Primer" the two message exchange concepts are called RPC-style and Conversational style, too. I think it does not matter if it is called conversational or document-oriented or message-oriented or anything else, as long as everybody knows what is meant.
For your information:
The message exchange concepts in the SOAP Primer is here: http://www.w3.org/TR/2003/REC-soap12-part0-20030624/#L1177
Posted by: Dominik Marks at March 8, 2006 4:19 PM
Nope, I still disagree. (Sorry for the late response). The document you linked to contains, e.g., this sentence:
"It is easy enough to see how such exchanges can build up to a multiple back-and-forth "conversational" message exchange pattern."
I'm convinced that a "conversation" implies an exchange of multiple messages that are correlated (which is a fine concept, but irrelevant here).
RPC means that an interaction with a remote service is treated like a procedure call, i.e. the network is abstracted away. In a message- or document-oriented interaction, the sending and receiving of a message is explicit (i.e. the developer is aware that he or she is sending a message),
Posted by: Stefan Tilkov at March 22, 2006 10:54 PM
Good idea!
P.S. A U realy girl?
Posted by: Memmorium at April 11, 2008 4:48 PM
my pics
Posted by: mypicst at April 12, 2008 2:13 PM
U need antivirus?
Posted by: antivirkaspersky7 at April 25, 2008 3:13 PM
I not understend what U want
Posted by: Вечерний макияж глаз фото at May 15, 2008 11:49 AM
давайте займемся этим!
Posted by: секс at May 16, 2008 12:28 PM
my girl crazy, man!
Posted by: crack at May 27, 2008 1:58 AM
my girl crazy, man!
Posted by: crack at May 27, 2008 1:59 AM