[Users] Categories of wizards for Service-Unit projects

[vzurczak]

Hi,

I have finally changed the use cases.
Like I previously said, a component may be present in several use case categories.
There are 6 of them now:
	
Communication gathers all the Petals components in charge of enabling communication between the bus and external applications or systems.
	
Service composition includes all the components that can be used to compose, orchestrate or assemble services.
	
Manual implementation lists all the components that allow one to implement its own Petals service.
	And 
Miscellaneous groups the other ones.


The last two ones are transversal.
	
Integration project lists the components (service engines mostly) that should be used in integration projects. It means these components do not need WSDL definition.
	
SOA project lists the components that should be used in a SOA context (meaning they rely on WSDL definitions).

[Image: http://img406.imageshack.us/img406/1672/usecases1.jpg ]

[Image: http://img829.imageshack.us/img829/4553/usecases2.jpg ]

Applicative integration and SOA are two facets of Petals capabilities.
Both kind of projects can coexist within a same bus instance. However, mixing both kinds of components to achieve a single process is quite risked.
They are not made to work together. Or not without respecting some constraints. 
Communication components (binding components) should work with both modes (integration and SOA contexts).

I think that could be an interesting white paper.  [Idea]




-------------------- m2f --------------------

Subscribe/Unsubscribe emails notifications :
http://forum.petalslink.com/m2f_usercp.php

Response to this email will be posted on the Petals forum.
Please delete the existing text before responding :)

Read the topic online:
http://forum.petalslink.com/viewtopic.php?p=31639#31639

-------------------- m2f --------------------