Jump to: navigation, search

Difference between revisions of "BPS35"

(New page: == Pass-through of External Context Objects to ODA Data Providers (BPS35) == The Open Data Access (ODA) runtime API is a self-encapsulating framework. However, when used as an embedded c...)
 
 
(One intermediate revision by one other user not shown)
Line 1: Line 1:
== Pass-through of External Context Objects to ODA Data Providers (BPS35) ==
+
== Pass-through of External Context Objects to ODA Data Providers ==
  
 
The Open Data Access (ODA) runtime API is a self-encapsulating framework.  However, when used as an embedded component in an application server, it would be useful to provide the capability to dynamically pass in external objects through an ODA consumer's runtime engine and into a custom ODA data provider (driver).   
 
The Open Data Access (ODA) runtime API is a self-encapsulating framework.  However, when used as an embedded component in an application server, it would be useful to provide the capability to dynamically pass in external objects through an ODA consumer's runtime engine and into a custom ODA data provider (driver).   
Line 9: Line 9:
 
== Specification Document(s) ==
 
== Specification Document(s) ==
  
* [http://www.eclipse.org/birt/release20specs/BPS35_ODAPassThruContext_SPEC.pdf  Project Specification]
+
* [http://www.eclipse.org/birt/release20specs/BPS35_ODAPassThruContext_SPEC.pdf  Project Specification and Related BIRT Engine API ]
 +
 
 +
[[Category:BIRT BPS]]

Latest revision as of 15:40, 29 October 2007

Pass-through of External Context Objects to ODA Data Providers

The Open Data Access (ODA) runtime API is a self-encapsulating framework. However, when used as an embedded component in an application server, it would be useful to provide the capability to dynamically pass in external objects through an ODA consumer's runtime engine and into a custom ODA data provider (driver).

Specification Lead

Linda Chan

Specification Document(s)