For my needs, a user definded DataContext-Class
as property in the modeler would help a lot ...
Andrus Adamchik <andru..bjectstyle.org> schrieb am 08.12.04 01:45:42:
>
>
> On Dec 7, 2004, at 3:41 AM, Jürgen Saar wrote:
>
> > Yeah, that's a good idea ...
> >
> > Mike Kienenberger <mkienen..laska.net> schrieb am 07.12.04 00:57:43:
> >>
> >> In the recent past, I also have wished to subclass DataContext for a
> >> couple
> >> of different situations.
> >> Can we consider creating a DataContextFactory class to provide this
> >> functionality transparently?
> >>
> >> -Mike
>
> Hmm... as DataDomain is a de-facto DataContext factory, I wonder if we
> should start by simply specifying custom DataContext subclass as a
> property in the model? Or should it be a name of a factory class for
> ultimate flexibility?
>
> Andrus
__________________________________________________________
Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201
This archive was generated by hypermail 2.0.0 : Wed Dec 08 2004 - 03:57:09 EST