At 22:43 03/10/2006, Jeremy Boynes wrote:
I think there's a big difference between something like
<implementation.jpa> and <implementation.das>

I think <implementation.jpa> is about simplifying the configuration
of a complex component with a specific service interface (in this
case EntityManager). SCA assembly allows you to do this and although
it may seem odd, it is valid. We may suggest alternatives but in the
end providing the freedom for users to choose is essential to our
success.

I'm probably going to reveal my ignorance here, but here goes ...

SCA/Tuscany, like any integration technology, is, I'm sure, going to run into the "who maintains the connectors/adapters/extensions" problem pretty quickly. You know the one - Vendor A creates an integration technology and then starts to build out adapters using this technology to other technologies that customers are interested in. Pretty soon Vendor A finds out that this is enormously expensive - not just in doing it initially but in keeping it up-to-date. So vendor A tries to push the onus onto Vendor's B, C and D to maintain the adapters. But B,C and D like a different technology and so the integration dies.

In the end customers lose out, because the integration never quite did what they could do with the vanilla product anyway. To my mind there are three ways of solving this:

a) don't provide any integration and just assume customers will use APIs directly
b) provide minimal, generic configuration-driven integration.
c) rely on some third-party integration technology that has enough critical mass to be kept up-to-date.

All of these have the advantage that not-only do you not have to build specific integrations, but you do not have to test them on specific platforms.

My opinion only.

andy
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to