Never mind!!
I found a bug in one of my support classes!
Thanks anyway,
Daniel
Daniel R. Ambrosio wrote:
Hello guys,
I am using OJB rc3.
I pasted the mapping I use in my application below. The problem is the
following: when I try to created an entry of ObligatoryProfileEntity I
would expect t
It worked out setting the collection-class to ManageableVector
Thank you all.
- Original Message -
From: "sclark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, September 25, 2003 12:08 PM
Subject: Re: problem with n:m collection
> This is because the default behavior wa
Hi Michael,
I have applied your patch. I don't inderstand why does this make difference,
which collection type is used internally by prefetcher, but I also don't see
any drawbacks of your changes.
Regards,
Oleg
On Wednesday 24 September 2003 17:11, Michael Schulze wrote:
> Hi again,
>
> sorry
Hi all,
The only driver working fine (for me, using PB API) with MS SQL Server 7 is
JSQLConnect.
Try last jtds from source forge, seems to work, can get collection by query but
have exception when try to get object by query (working fine with
JSQLConnect)
Why ? Any idea ?
here is my repository_da
This is because the default behavior was recently changed; collections now use
RemovalAwareCollection by default, which has the effect of deleting the
contained object as well as the relationship. The fix is to specify a different
ManageableCollection implementation in the collection-class attr
Hello guys,
I am using OJB rc3.
I pasted the mapping I use in my application below.
The problem is the following: when I try to created an entry of
ObligatoryProfileEntity I would expect that the reference field
ObligatoryProfileURLEntity.url create the entry in the URL table, and
just then it
I had this same problem. I'm wondering why this isn't the default
behavior of OJB?
When a new object is saved, all of the references need to be inserted, so
it doesn't matter what the collection is. After that, all work will be
against a materialized collection.
If this has been hash
Hi
can be it is a solution with you to see
Add in Class-descriptor
collection-class="org.apache.ojb.broker.util.collections.ManageableVecto
r"
-Original Message-
From: Martín Capriotti APTIX [mailto:[EMAIL PROTECTED]
Sent: jeudi 25 septembre 2003 17:02
To: [EMAIL PROTECTED]
Subject: pr
Hi
I have problems with n:m mappings, it is deleting the referenced objets instead of
deleting only the reference (when I delete it from the collection)
(behaving as if auto-delete="true" is set)
Example:
one way n:m direct mapping from Roles to Usuario (nothing mapped from Usuario to Rol)
---
Is there an FAQ out there that'll show me how to use XDoclet to generate
my .xml for my mappings? That'd be great.
--
andy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi guys, i´m new here and i don´t kow how to execute Stored Procedures
using OJB.
My DB is Sql Server 2000,
Please , help me ..
Tks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Stephen,
if you obtain a PB within odmg-api never
do a PB.close() - this is all handled by the
odmg-api.
> broker = ((TransactionImpl) tx).getBroker();
use it, but don't close it (or commit it).
odmg-api is set on top of pb-api.
regards,
Armin
- Original Message -
From: "Stephen Ting"
Sorry I have to reopen this case. after I try to dig more and again
encounter some errors when I try to acquire a pb from a active
transaction.
db = odmg.newDatabase();
db.open(site.getDbConnectionAlias(),Database.OPEN_READ_WRITE);
Transaction tx = odmg.currentTransaction()
[EMAIL PROTECTED] wrote:
> A question for the experts:
>
> I am using the ODMG API (RC4) with setting ImplicitLocking=false in
> OJB.properties.
>
> When I obtain a READ lock on an object that has proxy references, all
> proxies are getting materialized. Due to above setting, there are no
> READ
A question for the experts:
I am using the ODMG API (RC4) with setting ImplicitLocking=false in
OJB.properties.
When I obtain a READ lock on an object that has proxy references, all
proxies are getting materialized. Due to above setting, there are no READ
locks put on the referenced objects, s
Yeah!!! After I upgrade to rc4 this errors gone...
Thanks
>-Original Message-
>From: Stephen Ting [mailto:[EMAIL PROTECTED]
>Sent: 25 September 2003 08:49
>To: 'Ojb Users List'
>Subject: multithread problems using ODMG api
>
>
>
>I have problems in using OJB ODMG api in ejb system. When
16 matches
Mail list logo