|
He is evading the tough questions. he just mentions
that web service may be used for "complicated
task that can span several business
>
processes.>>"
But fails to mention which complicted
work?
I think most of those complicated work is done by
object/component middleware.
regards,
----- Original Message -----
Sent: Tuesday, May 31, 2005 5:42 PM
Subject: Re:
[service-orientated-architecture] Tutorial: Constructing Services with
Java
I'd say that this perspective is typical of a lot of J2EE
developers.
They get that services might be bigger than a component, but
they
really don't get document-oriented or loose coupling.
On
5/29/05, Shashank <[EMAIL PROTECTED]>
wrote:
>
> -------------
> There are many definitions
for web services, but in simple terms, web
> services are self-contained
and self-describing components that can be
> published, discovered, and
invoked across the network. A web service,
> as shown in Figure 1, may
perform a simple function, such as checking
> a credit history, or a
complicated task that can span several business
>
processes.>>
>
> -----------
>
>
So u define web services as "component" ?
>
> Also
can a web services b distributed like a "component"?
>
> Also can we use web service for developing stateful applications?
>
>
>
>
________________________________
> Yahoo! Groups
Links
>
>
> To visit your group on the web, go
to:
> http://groups.yahoo.com/group/service-orientated-architecture/
>
> To unsubscribe from this group, send an email to:
>
[EMAIL PROTECTED]
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.
Yahoo! Groups Links
|
