One of my favourite ommisions in all of these "SOA" tools is how many have nothing that actually enables you to model the service architecture bit.  You can define a WSDL, a BPEL or any number of technical or process elements, but never it seems actually create a service architecture.



On 29/08/06, Hitoshi Ozawa <[EMAIL PROTECTED]> wrote:

I agree that there are many "SOA tools" out there which just have
SOA in there names but do nothing else. But isn't this an issue
of picking the right tool and on using it correctly? The point I want to
make is that only few people in a project needs to be the "selector"
of tools for a project and create usage guidelines on using the tool.

I'm not saying there is no need for an expert but that there is no need
for everyone involved in a project to be experts.

H.Ozawa



Anne Thomas Manes wrote:

> Another issue that can't be addressed by tools:
>
> When building service-oriented systems, you don't want to make
> everything a service. Only those bits that are reusable should be
> exposed as services. Unfortunately, most of the current tooling out
> there tends to simply convert object interfaces into service interfaces.
>
> Anne
>
>
>
>


__._,_.___


SPONSORED LINKS
Computer software program Computer software spy Computer job
Database software Discount computer software


YAHOO! GROUPS LINKS




__,_._,___

Reply via email to