I don't see this an issue if SOA is built on Component
technology. Since f(x) is implemented at the level of
Component and if a change of f(x) does not change the
COM interfaces, then nothing changes. If a change of
f(x) changes the COM interfaces, by rule, we create a
new COM interface to incorporate the change of f(x). 
Accordingly interfaces at Service level also changes. 
By no means this change shall break the current users
who just donot know the new interface and act as
nothing happened.  new users that are aware of the new
interfaces will use the updated features.  

I see things like SOA being not OO.  Because currently
the practice of SOA does not follow the evolution of
computer technology that new evolutions build on the
older ones hence inherit older technology features.  I
see the discussions of many issues on SOA here are
really issues already solved with OO and COM.   There
is no such thing as quick and dirty.  If it is dirty
it is not quick.  It is quick when it is clearn.
Clearn means concise and less and be able to do more.

Jerry

--- James Taylor <[EMAIL PROTECTED]> wrote:

> --- In service-orientated-
> [EMAIL PROTECTED], "jeffrschneider"
> <[EMAIL PROTECTED]> 
> wrote:
> >
> > If the logic in a service is changed and f(x)
> begins producing a 
> new 
> > result, do you version the service?
> > 
> > (Note: in this scenario, the interface didn't
> change just the 
> internal 
> > logic.)
> > 
> > Thanks,
> > Jeff
> >
> I think the question has two answers - if the
> changes impact the 
> business purpose of the service, yes, otherwise no.
> If the service 
> provides the same business decision it did before,
> no consumer should 
> need to worry. Check out this post for a little more
> on this: 
>
http://www.ebizq.net/blogs/decision_management/2006/10/agile_services_
> business_rules.php
> 
> 
> 
> 
> 
> 
> 
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 





 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/service-orientated-architecture/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/service-orientated-architecture/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[EMAIL PROTECTED] 
    mailto:[EMAIL PROTECTED]

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
 



Reply via email to