Hi Brian,
if this issue isn't the same as in your later post "Expected Extent
Behavior?" and does not mix different inheritance strategies (which is
not supported), please provide a more detailed description so that I can
implement a test case to reproduce the issue.
regards,
Armin
Brian La
Hi Brian,
Brian Latimer wrote:
I have an Interface "I"
It has implementing classes A, B, and C
Classes B and C both extend class A and have a super reference to it.
If use the following:
when I search via getCollectionByQuery for instances of "I" then I get
back instances of B
>
> I think OTM is kind of "deprecated", but i don't know if it's important
> for
> this issue.
> In my mind when you do a commit a transaction, if something fails, no step
> of the transaction should have been commited, so maybe your database
> do not support transactions.
>
>
I also wonder what t
I think OTM is kind of "deprecated", but i don't know if it's important for
this issue.
In my mind when you do a commit a transaction, if something fails, no step
of the transaction should have been commited, so maybe your database
do not support transactions.
2006/2/21, Vamsi Atluri <[EMAIL PROT
Thank you, Armin, I think i'am gonna try to use OJB 1.0.4, and if it does
not work i'll post details about my issue.
Jean-Yves
2006/2/21, Armin Waibel <[EMAIL PROTECTED]>:
>
> Hi Jean-Yves,
>
> Jean-Yves Sironneau wrote:
> > Hello, I have a few unrelated questions regarding OJB :
> >
> > - Is th
Dear all,
I am working on a j2ee web application using OJB
(db-ojb-1.0.2) as persistence layer.
The application server is oracle oc4j. The application
is perfectly working on
oc4j v9.0.3.0.0 and v9.0.4.0.0 (both enterprise and
standalone versions). If I try to deploy
the application on oc4j v9.
