Hi Kelvin, your advise was correct - I removed the dynamic registration (XSDHelper.define..) and then it worked.
Thanks for your help, Erich **** Hi Erich, it sounds to me like you have managed to register the types dynamically (perhaps as well as statically); i.e. in addition to a call to SDOUtil.registerStaticTypes(FactoryThatCreatesPersonClassesEtc.class); I think you must have a call to something like XSDHelper.INSTANCE.define(input_stream_from_SchemaThatDefinesPersonTypeEtc); somewhere, and that would seem to be masking the static defintion on Type lookup In answer to your question, if, when using the dynamic API to create a DataObject, the Type of data object that you are creating was registered statically, then, as you suggest ought to be the case above, you can use either the static or the dynamic APIs on that data object. If however the type was registered dynamically, then you can only use the dynamic api. Regards, Kelvin. On 15/12/06, Erich Rueede <[EMAIL PROTECTED]> wrote: > > Hi all, > > I'm referring to Philipp Schöpfs questions about instantiating a static > SDO through the DataFactory.INSTANCE.create(Person.class) method. > > This works without exception for me BUT the actual object created is not > static but dynamic (DynamicDataObjectImpl) and therefore it cannot be > type- > casted to "Person". I actually expected a "PersonImpl" to be returned... > > So the question is: > Is it possible to use the dynamic API to create an SDO and then > subsequently > switch to a static type of processing? This actually works with the > EMF-based > SDO 1.0 implementation. > > Thanks, > > Erich __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
