Hi Andrew,
On 02/03/2008, at 4:02 PM, Andrew Lindesay wrote:
Yes I had selected the correct prototype as per your screenshot and
I believe that in WO 5.4.X, it should use this prototype based on
the JDBC plugin, but it has not used the prototype at model load time.
Hmm. Okay - I've not used WO5.4 yet, so I'm not sure what might be
happening. Are you setting a differing connection dictionary at
runtime? If so perhaps you're overriding what's in the model(?).
It works fine for EOJDBCPrototypes. I am not using ProjectWonder.
cheers.
I'm getting to grips with prototypes (which I should have used
earlier now I see how handy they are), but am having a bit of
trouble with WO 5.4. I can create a "EOJDBCPrototypes" entity
and that works just fine, but if I create an
"EOJDBCPostgresqlPrototypes" then it doesn't get picked up even
with the model's plugin set to "PostgresqlPlugIn". I think I
have this right?
if you haven't already, you might want to have a look at Wonder's
ERPrototypes as an example. Are you saying, however, that you're
unable to select EOJDBCPostgresqlPrototypes (similar to attached
image) or that it's not happening at runtime?
with regards,
--
Lachlan Deck
_______________________________________________
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]
