Hi Luciano,
I didn't see any other replies to your email, so I'll give you my two cents.
My first inclination for Stored Procedures in SCA is as component
implementations. The binding for a STP would be related to the mechanism
that a particular DB uses to invoke STPs. In Java, one might be tempted to
think that JDBC is analogous to a binding, but the analogy falls apart (as
in the JMS case) because JDBC is an API. Further, providing a JDBC binding
in SCA might be better done by a DAS anyway, which you're already familiar
with. When SCA talks about supporting components across varied and
homogeneous runtimes, STPs are often used as an example to drive the point
home.
How hard would this be to prototype in OS?
- Dave
----- Original Message -----
From: "Luciano Resende" <[EMAIL PROTECTED]>
To: "tuscany-dev" <[email protected]>
Sent: Wednesday, November 08, 2006 11:38 AM
Subject: SCA Binder question
I was reading the SCA specs around what is the concept of a Binder, and my
understanding is that it's more towards the transport protocol layer. If
this is the case, how would we have a Stored Procedure as a Binder ?
SCA spec :
http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-sca/SCA_AssemblyModel_V09.pdf
page 45: "SCA supports the use of multiple different types of bindings.
Examples include SCA service,
Web service, stateless session EJB, data base stored procedure, EIS
service."
Could someone elaborate little more on how the SP would be used as a
binder
?
- Luciano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
