CSC/ECE 517 Fall 2009/wiki2 17 va

!!!! I have copied things that help with formatting the page from my prior wiki. Feel free to add in anything that you think may help with formatting from your project.

!!!! Main topic (to keep us on track):

!!!! Note: Delete all the !!!! parts when done. These are notes while developing the wiki.

!!!! SOA provides another view of providing functionality based upon services offered in terms of protocols and a specific API. To provide services, platforms rely upon principles and the power that can be expressed through reflection and meta programming. Research and report how these critical concepts relate to and support SOA.

!!!! Reword the following paragraph to "sound better"

Reflection and metaprogramming relate to and support use of a Service Oriented Architecture 3 (or SOA). The first goal of this article are to provide a simple understanding of reflection, metaprogramming, and SOA's. The next goal is to explain how these concepts are interrelated. The final goal is to examine how reflection and metaprogramming supports SOA's.

An overview of the concepts

Service Oriented Architectures

Service Oriented Architecture (or SOA) is a concept in computing that defines the interaction of different software in terms of protocols and functionality. A SOA can be viewed as containing multiple services which may be linked as desired by protocols. SOA is designed so that each functional unit of software in a system is isolated from each other and provides a service without directly making subroutine calls to each other. This may be accomplished with the use of messages 3

!!!! If we can, find a way to make the footnote in brackets, without brackets will probably work though. !!!! Did you intend to say "subroutine calls" above? I changed it from calls to subroutine calls because the topics did not appear to match.

The information being used to communicate between services must contain sufficient detail about the characteristic of the data and the data itself and must remain independent of the underlying platform and programming language. Although SOA does not specify the format to transfer data, programmers have generally used XML for this purpose. However, metadata (data that describes the actual data) in the SOA must: 3

!!!! Here is what I got out of it, that was a hard definition to struggle with :-) See if you agree with this and if so, remove this note.

• Be easy to configure
• Provide an easy way to discover services
• Provide an easy way to incorporate services
• Remain coherent
• Preserve data integrity
• Be easy to manage

A simple example of metadata is a README file that specifies the inputs and outputs to a program. The inputs and outputs of the program would be the data, and the README describes this data.

SOA also does not limit the protocol used to transfer the data and a wide variety of technologies can be used including SOAP, REST and RPC. This is generally left for the programmer of the system.

!!!! It may be a good idea to add a graphical example of a SOA here

Metaprogramming

!!!! Discuss metaprogramming !!!! It may be good to include a programming example here

Reflection

Reflection is a specific type of meta-programming and emphasizes on dynamic program modification. The concept of reflection can be used to extend the service being provided by a system in a Service-oriented Architecture by allowing the transfered data to modify the behavior.

• Example: Reflection in Perl 5

 # without reflection
 my $foo = Foo->new();
 $foo->hello();

 # with reflection
 my $class  = "Foo";
 my $method = "hello";
 my $object = $class->new();
 $object->$method();

In the example with reflection, $object and $method can be determined and even changed at run time. This allows the program to change its own behavior.

How it is all related

!!!! Explain

Enhancing SOA

Service-oriented Architecture becomes greatly effective when the underlying programs are able to dynamically adapt to the data received. Two very important concepts support this principles that SOA is build upon:

1. Metaprogramming - Programs that write and manipulate other programs
2. Reflection - Programs that modify their own behavior

Appendix

Metadata - data that describes the actual data

References

1. http://www.service-architecture.com/web-services/articles/service-oriented_architecture_soa_definition.html - Brief explanation of SOA

2. Thomas, Dave (2006). Programming Ruby, The Pragmatic Programmers' Guide.

3. http://en.wikipedia.org/wiki/Service_oriented_architecture - A very detailed explanation of SOA

4. http://www.javaworld.com/javaworld/jw-06-2005/jw-0613-soa.html - A more easy to understand explanation of SOA

5. http://en.wikipedia.org/wiki/Reflection_(computer_science) - Explanation of Reflection

!!!! Remove the title below if we do not have any good external links.