Sebastien,
There's the basis of a Java interface to SDO generator at [1] but it
hasn't been developed to a working state and hasn't been looked since
the initial drop of code into Tuscany. It would be great to get this
or similar function up and running.
If you take a look at the noInterfaces
I missed you last point in my reply. getStaticType() is required to
underpin fundamental EMF behaviour. Without it EMF's capacity to know
the class of an EObject (which all our DataObjects are derived from)
is broken for all static classes, and that would break many SDO
behaviours, e.g.
Hi Sebastien,
One thing to note is that the static SDO supported in Tuscany today is an
EMF-style pattern that is intended to be the highest performance in-memory
static DataObjects. Other less-performant patterns, that use a dynamic
(DataObject) proxy, for example, are possible and probably
kelvin goodson wrote:
Sebastien,
There's the basis of a Java interface to SDO generator at [1] but it
hasn't been developed to a working state and hasn't been looked since
the initial drop of code into Tuscany. It would be great to get this
or similar function up and running.
If you take a
kelvin goodson wrote:
I missed you last point in my reply. getStaticType() is required to
underpin fundamental EMF behaviour. Without it EMF's capacity to know
the class of an EObject (which all our DataObjects are derived from)
is broken for all static classes, and that would break many SDO
Sebastien,
You're generic implementation is fine as long as TypeHelper.INSTANCE is
the right scope where the type is registered.
If you aren't interested in supporting dynamic subclasses of static
classes, then getStaticType() is always == DataObject.getType(), so you
might not even need to
kelvin goodson wrote:
If you are discounting using XSD for the source of metadata to
describe the SDO types then there is the SDO API provided for dynamic
metadata creation. The sample at [1] gives an introduction to this.
The paper at [2] discusses the subject also, and the program
underlying
If you are discounting using XSD for the source of metadata to
describe the SDO types then there is the SDO API provided for dynamic
metadata creation. The sample at [1] gives an introduction to this.
The paper at [2] discusses the subject also, and the program
underlying the discussion in the
The online store tutorial currently uses a simple handwritten JavaBean
to represent the Items in the store catalog and shopping cart. I'm able
to flow that Item bean over local calls, WS, Atom and JSON bindings.
Here's what it looks like: