So silly me I googled OracleDriver webobjects and I found a webobjects-dev mail archive that was exactly what I needed. And then I noticed that I started it in 2012. So I found this and I have the properties working.
# Connection Dictionary SilentPartner.URL=jdbc:oracle:thin:@10.1.3.250:1521/XE SilentPartner.DBUser=name SilentPartner.DBPassword=PW SilentPartner.DBPlugin=OraclePlugIn Where SilentPartner.eomodel is the model file in the framework! So I took the connection dictionary out of the model after all. Thanks for reminding me to keep at it till I figured it out. Ted > On Oct 29, 2016, at 8:37 PM, Paul Hoadley <pa...@logicsquad.net> wrote: > > Hi Ted, > > With the caveat that I don’t use Oracle (though that’s probably incidental)... > > On 29 Oct 2016, at 10:26 PM, Theodore Petrosky <tedp...@yahoo.com> wrote: > >> So I went back to the original app that was using a framework for the oracle >> connection and I commented out the property file entries for the global >> database. then I went to the framework and added the connection information >> to the Entity Modeler instance, and now that works. >> >> What does that mean? I should not use the properties file for my connection >> dictionary? > > On the contrary, I think you should _only_ use Properties for your connection > dictionary. One place, you know where it is, you can potentially override it > when you need to (for example, with Properties.dev and Properties.ted). > >> Let’s think. I had the connection dictionary in the Entity Modeler instance >> to reverse engineer the database. Then I deleted the entries in EM, and >> added the GLOBAL lines to the properties file in my app. >> >> Somehow, even though I deleted the lines in the EM instance, the framework >> was remembering and Chuck was asking, “Is it finding a different model >> somewhere?” >> >> But I selected but my app, and the framework in Eclipse, cleaned them and >> even right clicked and refreshed. > > It’s hard to say what was going on here. > >> Should I just call this voodoo and move on? > > I’d call it voodoo, but if it was me I would press on until I had the > connection dictionary out of the model and into Properties, especially if, as > you say, the model is in a framework. (How can you set the connection > dictionary in the framework and be confident that will be appropriate for > every app that uses the framework?) > > > -- > Paul Hoadley > http://logicsquad.net/ > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
