Great!
Thanks Armin and Jakob.
Happy user again,
Chris :)
-Original Message-
From: Armin Waibel [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 05, 2006 6:08 AM
To: OJB Users List
Subject: Re: OJB and the X-Files... :)
Hi Chris,
it was fixed (by Jakob) in OJB_1_0_RELEASE branch and
Hi
This mail is just to ask about projects of OJB Team about EJB3.
Now specification seems to me completed and stable and some OJB competitors
has offer.
EJB3 same already to be a standard.
This seems to me a critical question about OJB future.
Any answer welcome
Andre
OJB runs outside of a container, it is not really comparable. Also ojb
criteria api is way better then anything out there. I like to stay far from
things like
select object(o) from Book o where lower(o.title) like '%java%'.
regards,
Dennis
2006/3/6, Hale India [EMAIL PROTECTED]:
Hi
This
Hi Bruno,
Bruno CROS wrote:
Our first problem was, that, after commit, P1 was not referencing M in
database. I deduced that after a flush(), new locked objects (before
flush)
can't reference new ones created before flush too (a second time). Humm,
strange... we check all code : No apparent
Hi,
I'm trying to work with Derby, but I'm not sure which DB to use for the
torque.database property.
Looking at the torque-gen I see there is a cloudscape, is cloudscape the
name to set? Any other special configuration needed? Is there any
example to follow?
Sean C. McCarthy
This issue was related to the fact that we are using XAPool. Here is
the explanation from the experts. I've cc'd them in case you have any
questions. They patched our OJB 1.0.4 jar as a temporary solution.
_
The problem here is the
On 3/7/06, Byrne, Ailish M [EMAIL PROTECTED] wrote:
This issue was related to the fact that we are using XAPool. Here is
the explanation from the experts. I've cc'd them in case you have any
questions. They patched our OJB 1.0.4 jar as a temporary solution.
