Thanks again, (for about a zillionth time)!
That was precisely the culprit; fixed and works like a charm.
(Having found it, I even can track it back to a mistake when batch-renaming
dupped entities, so no mystery anymore.)
All the best,
OC
On 23. 2. 2016, at 21:53, Chuck Hill wrote:
> grep
grep -ir jceb *
Try that. There is an adaptorName setting in the index.eomodeld file that can
be used for this. It forms it as “Java” + adaptorName() + “Adaptor”
Chuck
On 2016-02-23, 12:41 PM,
"webobjects-dev-bounces+chill=gevityinc@lists.apple.com on behalf of OC"
wrote:
>T,
>
>O
P.S. Here's the stack trace, perhaps it might help someone to see the culprit:
===
Caused by: java.lang.IllegalStateException: Unable to get the name of the class
to instantiate for the adaptor framework JavaJCEBCAdaptor. The possible causes
for this error are: the adaptor framework is not insta
T,
On 23. 2. 2016, at 21:29, T Worman wrote:
>> "Unable to get the name of the class to instantiate for the adaptor
>> framework JavaJCEBCAdaptor. The possible causes for this error are: the
>> adaptor framework is not installed on your system, the adaptor framework is
>> not linked into your
On Feb 23, 2016, at 12:21 PM, OC wrote:
>
> Hello there,
>
> well, I have cleaned up the external DB model so that it loads all right. At
> launch, I am setting the connection dictionaries:
>
> - all my normal models get
> [URL:jdbc:FrontBase://localhost/DBA/user=USER/isolation=read_committed/
Hello there,
well, I have cleaned up the external DB model so that it loads all right. At
launch, I am setting the connection dictionaries:
- all my normal models get
[URL:jdbc:FrontBase://localhost/DBA/user=USER/isolation=read_committed/locking=optimistic,
password:, username:]
- my import mod
In case it's helpful, there's ERXJDBCUtilities in Wonder which copies from one
DB to another.
Cheers, Anjo
> Am 22.02.2016 um 20:30 schrieb OC :
>
> Chuck,
>
> On 22. 2. 2016, at 19:18, Chuck Hill wrote:
>
>> It sounds to me like sharing the model would be less effort.
>
> Thanks!
>
>> R
Joins are just done by following relationships, but as with fetching EOs you
need to do one fetch per entity (or entity hierarchy). Otherwise, I think you
are correct that you need to use SQL. Or you could fetch them as EOs with
pre-fetching and then extract the dictionary from the snapshot of
Chuck,
On 22. 2. 2016, at 19:18, Chuck Hill wrote:
> It sounds to me like sharing the model would be less effort.
Thanks!
> Rather than use rawRowsForSQL you can just make regular fetch specs and tell
> them to fetch raw rows. You might get more data back than you need, but all
> the join a
It sounds to me like sharing the model would be less effort. Rather than use
rawRowsForSQL you can just make regular fetch specs and tell them to fetch raw
rows. You might get more data back than you need, but all the join and name
translation etc will be handled for you.
Chuck
On 2016-0
10 matches
Mail list logo
