Truth be told,
traditional approaches to
integration are really
about keeping persistence
at the points, within the
source or target systems,
and replicating data as
needed. However with the
use of true services,
there is a clear
advantage in keeping some
persistence at a
central-tier, for any
number of legitimate
reasons. Let's explore
this in the context of an
SOA.
Agility seems to be the
buzzword du jour. There
are 'agile enterprises,'
'agile manifestos,'
'agile programmers,' and
'agile architectures.'
Slap 'agile' in front of
just about anything and
marketers believe it will
sell better. Yet, one of
the primary goals of
using service-based
architectures was to
create 'agile systems.'
This begs the question,
was it just marketing or
is there something to it?
Working with
service-oriented
applications is a lot
like doing your taxes
because: there's really
no avoiding it, you need
to keep track of a number
of different factors, you
must maintain a record of
data to protect against
audits and plan for the
future, and you'd better
catch any mistakes or
you'll have a problem on
your hands faster than
you can spell 'SOA.'
Mindreef is making it
easier for Web services
problems to be resolved,
Mark Ericson - CTO of
Mindreef - told
SYS-CON.TV
(http://sys-con.tv) at
Web Services Edge 2005
recently in Boston. v4.1
of SOAPscope Web services
diagnostic tool allows
over-the-Web
collaboration between
developers.
IBM's 'Project Cinnamon,'
still in beta but due to
be released with IBM's
next DB2 release, will
put XML at the heart of
DB2 Content Manager and
allow customers to create
automatically the data
model of a database based
on the document type
definitions or XML
schemas they choose.
While widely adopted or
standardized security
protocols are great for
interoperability, a set
of SOAP message header
elements as well as a few
new elements that belong
in the message body are
outside the scope of the
existing mechanism for
publishing service
descriptions, which is
WSDL.
The momentum behind Web
services is building. If
you haven't heard about
them by now, you've
probably been living in a
jungle or some remote
area for the last few
years. The underlying
technologies of Web
services are XML, HTTP,
SOAP, WSDL, and UDDI. XML
provides an open standard
for data exchange, HTTP
an open transport
protocol, SOAP a remote
method invocation
protocol, WSDL the
service description
language, and UDDI a
service discovery and
registry.
SOAP, the Simple Object
Access Protocol, is a
lightweight toolkit for
building Web services. It
is an amalgam of
ubiquitous technologies -
HTTP and XML. Though the
likes of Microsoft, IBM,
and the Apache Software
Foundation normally have
little in common, all
support it as a
foundation for deploying
Web services. One of the
great advantages of
SOAP's lightweight nature
is the simplicity of
server-side programming.
A SOAP service needs no
knowledge of the SOAP
environment. In fact,
just about any Java class
that exposes public
methods can be turned
into a SOAP service.
Oct. 21, 2001 12:00 AM Reads: 14,899 Replies: 5
SUBSCRIBE TO OUR RSS FEEDS & GET YOUR SYS-CON NEWS LIVE!
Click to Add our RSS Feeds to the Service of Your Choice:
I took the advice of a
friend of mine and
steered clear of the
'normal' movie theaters
and went a little out of
the way to go to a DLP
movie theater. The
experience
There are 8,909 books
listed on Amazon.com with
the word 'Investing' in
the title; there are(!)
27,146 books with the
word investment in the
title. Without having lo
This book is an update of
an earlier version that
was written for SQL
Server 2000. It employs
the Murach approach of
dual pages that repeat
and enhance the concepts
Reviewers overuse the
phrase 'required
reading,' but no other
description fits the new
book 'Ajax Security'
(2007, Addison Wesley,
470p). This exhaustive
tome from B
In my many years of
programming, almost 20
years now, I have used
countless integrated
development environments
(IDEs). I have used
everything from a simple
text edi
About Newsfeeds / Video Feeds
Truth be told,
traditional approaches to
integration are really
about keeping persistence
at the points, within the
source or target systems,
and replicating data as
needed. However with the
use of true services,
there is a clear
advantage in keeping some
persistence at a
central-tier, for any
number of legitimate
reasons. Let's explore
this in the context of an
SOA. 
Agility seems to be the
buzzword du jour. There
are 'agile enterprises,'
'agile manifestos,'
'agile programmers,' and
'agile architectures.'
Slap 'agile' in front of
just about anything and
marketers believe it will
sell better. Yet, one of
the primary goals of
using service-based
architectures was to
create 'agile systems.'
This begs the question,
was it just marketing or
is there something to it?
Working with
service-oriented
applications is a lot
like doing your taxes
because: there's really
no avoiding it, you need
to keep track of a number
of different factors, you
must maintain a record of
data to protect against
audits and plan for the
future, and you'd better
catch any mistakes or
you'll have a problem on
your hands faster than
you can spell 'SOA.'
I took the advice of a
friend of mine and
steered clear of the
'normal' movie theaters
and went a little out of
the way to go to a DLP
movie theater. The
experience 
There are 8,909 books
listed on Amazon.com with
the word 'Investing' in
the title; there are(!)
27,146 books with the
word investment in the
title. Without having lo
This book is an update of
an earlier version that
was written for SQL
Server 2000. It employs
the Murach approach of
dual pages that repeat
and enhance the concepts 
Reviewers overuse the
phrase 'required
reading,' but no other
description fits the new
book 'Ajax Security'
(2007, Addison Wesley,
470p). This exhaustive
tome from B
In my many years of
programming, almost 20
years now, I have used
countless integrated
development environments
(IDEs). I have used
everything from a simple
text edi