[Users] Categories of wizards for Service-Unit projects

[vzurczak]

Hi,

Currently, the SU wizards allows you to choose among 3 categories of use cases:
	Provide or Import a service into Petals

	Consume or Call a Petals service

	Use a Petals technical service


[Image: http://img641.imageshack.us/img641/1309/petalsstudiotutoimportw.jpg ]

These categories were defined at the beginning of the Petals plug-ins, a long time before the studio was created.
Someone told me yesterday that these categories were not real categories of use cases. 
And indeed, when they were defined, they in fact matched a sub-set of Petals components.
+ Provide... was for Binding-Components that can be configured in provides mode.
+ Consume... was for Binding-Components that can be configured in consumes mode.
+ ... technical... was for Service Engines (the Quartz component did not exist at the time).

I had to agree with him.
In fact, the "provide" category should also contain wizards like XSLT and Validation.
Which would bring back the categories number to 2, instead of 3.

We could also imagine some components should be placed in a new category, because they provide a new service and consumes other services at the same time. Examples include BPEL, EIP, POJO and maybe Jsr-181. That could be an "Orchestration" category. In fact, nothing prevents a wizard from being in several categories. It is about use cases after all.

What do you think about it?
Would like to keep the current classification? Or would you prefer a different organization?
And if so, what use cases would you see?




-------------------- 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=31484#31484

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