OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

sca-c-cpp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: NWE ISSUE: Accessing SCA Services from non-SCA code

TARGET: C++ and C specificationa,

        Section titled "
Accessing Services from non-SCA component implementations" (3.2 of WD 04)


Code that is completely external to an SCA domain can communicate to SCA services through the externally advertised service bindings.


However, there is sometimes code that is deployed that shares much in common with the SCA domain. In increasing levels of coupling, the code might:

1. Have SCA APIs implemented to work with the target domain

2. The client code was deployed as part of an SCA deployment, but the code is not within an SCA component.

In either or both of these cases, we should provide a simple way for the client to access the target component.

The current specification implies that the client would accomplish this by retrieving a ComponentContext or SCAREF, although it does not describe what component to use for this purpose (after all, the client is not associated with a component).


Nothing yet.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect

Research Triangle Park,  NC
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]