Hi Frank,
thanks for the fast reply. Good to know that I don't need eyeglasses, yet;-)
I think I will stick on the EMF API and later switch to the SDO 2.1
featureset, as soon at it gets out.
----- Original Message -----
From: "Frank Budinsky" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, August 03, 2006 4:05 PM
Subject: Re: DataObject against XSD validation
Hi Philipp,
You've observed correctly a hole in the SDO spec version 2.0.1. There is
no API for reading XSD constraints on metaobjects. This is being addressed
in the SDO 2.1 spec, with the addition of two new methods on the Type and
Property interfaces:
List getInstanceProperties()
Object get(Property)
The XSD-constaints, and other user-defined annotations, will appear on the
metaobjects as instance properties (i.e., like open content). We plan to
start to implement some of the SDO 2.1 features in Tuscany as soon as the
spec is finalized (target is early September).
In the meantime, you're correct that the only way to retrieve the
constraints is using the underlying EMF API.
Frank.
Philipp Schöpf <[EMAIL PROTECTED]> wrote on 08/03/2006 06:47:17 AM:
Hi,
I am wondering how I can validate my (statically XSD- based
generated) DataObject against its XSD meta model. The spec is a bit
unclear about the validation support - on the one hand, it states
1.. Supports validation of the standard set of constraints
captured in the metadata. The metadata captures common constraints
expressible in XML Schema and relational models (for example,
occurrence constraints).
On the other hand I cannot find the API to validate my SDO objects
with. I could use the API of the underlying EMF framework, but that
is not what I am looking for.
Can anybody point me into the right direction?
Thanks in advance,
Philipp
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
