As far as how Wonder uses prototypes differently, Wonder (and now
5.4) have vendor-specific prototypes, meaning you can define
EOJDBCFrontBasePrototypes (or is it EOFrontBaseJDBCPrototypes ... I
never remember) and Entity Modeler and the runtime will
automatically "do the right thing" with those.
I think this is what is not happening for me. Entity Modeler appears
to work fine (subbing in the attribute configuration when i select a
prototype definition) but at runtime the model appears to use
EOJDBCPrototypes rather than EOJDBCMySQLPrototypes.
I'm guessing therefore I've just not got something "switched on" - are
there any wonder properties that need to be switched on ? I thought i
was just case of building the ERPrototypes framework, hooking it up to
the project, then specifying the prototypes to use in the connection
dictionary (or via ModelName.EOPrototypesEntity=EOJDBCMySQLPrototypes
when configuring the connection dictionary via properties).
Is that about right ? Are there any properties that need adjusting ?
How about these ones:
er.extensions.ERXModelGroup.prototypeModelNames
er.extensions.ERXModelGroup.flattenPrototypes
er.extensions.ERXModelGroup.patchModelsOnLoad
I'm just checking out the wonder source so i can stick some
breakpoints in the the ERXModelGroup to try and figure out why it's
not loading properly...
Thanks, Simon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
