I'm not sure I really understand what you're asking. There are 2 factories in the picture. The generated Factory that only knows how to create instances of the static SDO types, and the "ordinary" SDO DataFactory, that can be used to create instances of any type (static or dynamic). The second one is used in code that doesn't have static knowledge of the generated Java classes (for example, the loader).
Frank.
From: "Millies, Sebastian" <[email protected]>
To: <[email protected]>
Date: 10/05/2010 01:54 PM
Subject: FW: [SDO] Samples for notification feature / register ?
Hello Frank,
I am not sure I understand.
I can call register(HelperContext) only after loading the factory class
and obtaining an instance. For example, I could modify the static init()
method
to call instance.register(getScopeFromSomewhere()). Afterwards I could call
scope.getDataFactory(type) and so on.
But what would be the purpose of obtaining a data factory in such a
roundabout
way? If I have to obtain an instance of the factory for the type in the
first place,
why should I not always use factory.create() directly?
-- Sebastian
From: Frank Budinsky [mailto:[email protected]]
Sent: Tuesday, October 05, 2010 4:31 PM
To: [email protected]
Subject: Re: [SDO] Samples for notification feature / register ?
[snip]
For your second question, Factory.register() is used to define types with
static implementation classes. Load from XSD is used for dynamic SDO types.
Frank
<<inline: graycol.gif>>
<<inline: ecblank.gif>>
