--- In [email protected], Michael Poulin <[EMAIL PROTECTED]> wrote: > > Yes, it was deliberate overstatement though based on OASIS SOA RM standard. > When I talk with people who see value in SOA Projects, I usually one of two cases (sometimes, both): > 1) it is just an initial first pilot project 'to taste the water', and it is OK > 2) Web Services are used for application integration w/o going into real SOA value of business functionality > > Actually, I do not mind having SOA projects but only AFTER the overall business functionality picture and SOA environment are in place: think/see globally and move locally.
Yes, thinking globally and acting locally boils it down nicely. But the reality is there is so much project-level development going on that the project group can't wait around for a global SOA intiative, if one even exists. So what advice would you give them? I would say Paul's advice, along with his 4 point clarification, is a good start. In a nutshell, define common messages as the basis of the interface for an endpoint, using XML Schema, with an eye towards using or building a canonical model (e.g. a "Customer"). Without this guidance, you'll end up with JBOWS with little or no reuse and agility, and you'll add to the chaos that will have to be fixed eventually. -Kirstan
