Could you please explain how "SCA" help you directly to solve the lazy-association data graph loading by the proxy pattern inside  of DTOs (if it was your question) ?

As i know :
"Service Component architecture  (SCA) is a set of specifications which describe a model for building applications and systems using a Service-Oriented Architecture. SCA extends and complements prior approaches to implementing services, and SCA builds on open standards such as Web services."

"Service Data Objects (SDO) are designed to simplify and unify the way in which applications handle data. Using SDO, application  programmers can uniformly access and manipulate data from heterogeneous data sources, including relational databases, XML data sources, Web services, and enterprise information systems."

SCA and SDO can each be used on their own - there is no requirement to use both of them in the same application. SCA and SDO used together provide a powerful and flexible way of building applications around a service-oriented architecture and some experts believe this combination ( SCA + SDO) makes the next-generation SOAs.



DTOs can be propagated from Client-tier to Integration-tier, they are in all tiers and layers so whenever about the lazy-association data graph loading or persisting is talked, it doesn't mean has been just mentioned about the persistent layer or ORMs , obviously they can be loaded by your own service  out of the persistence-context (e.g. in the service consumer side ).