Re: general prototype questions
Re: general prototype questions
- Subject: Re: general prototype questions
- From: Mike Schrag <email@hidden>
- Date: Tue, 29 Jul 2008 14:44:06 -0400
Under normal circumstances, switching according to prototype "just
works". You will need to tell EOF which connection dictionary, and
therefore database plugin, to use, but that is all.
If you're just taking Wonder's, then in 5.4.x, you can just drop it
in. However, if you're in 5.3 (without Wonder), then you will need to
pick the vendor-specific entity from ERPrototypes and set that as your
EOJDBCPrototypes entity. Wonder has (which 5.4 also added) support
for vendor-specific prototypes -- EOFrontBaseJDBCPrototypes (or
EOJDBCFrontBasePrototypes -- I don't recall the order offhand). 5.3
EOF normally only supports adaptor-specific prototypes
(EOJDBCPrototypes), which means you need to drop in the one you want
for the database you're using. If you're using Wonder, it does this
magically.
OK, but then EOF must be capable of determining which prototype
entity to use during runtime (hence the "prototypeEntityName" prop
in index.eomodeld of a model bundle). Which makes sense, but in that
case the chapter in Practical WO on Prototypes does not make sense,
since it gets into solving exactly that problem. So, has EOF evolved
since Practical WO was written in this regard? Or was the problem in
the old EOModeler (since it did not IIRC allow one to change the
"prototypeEntityName" setting, so one was stuck with the EO<adaptor
name>Prototypes, meaning EOJDBCPrototypes )?
prototypeEntityName is not part of the EOModel specification, it's
something Entity Modeler adds that is co-supported in Project Wonder.
EOF (give or take) scans your model group looking for entities named
EOPrototypes, EO<adaptor>Prototypes and a couple others and takes all
the attributes of those and unions them together to form the set of
prototype attributes that are available to you. prototypeEntityName
is a mechanism that wonder provides to SPECIFICALLY override this
behavior, which allows for some slightly crazier, but powerful
abilities like using two different vendor databases at runtime with
the same set of prototype models (which normally wouldn't work right,
because of the way prototype attributes are resolved).
Or am I missing something obvious?
missing, yes; obvious, no so much :)
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden