Question - Mapping Classes on Multiple Joined Tables

Hello, Is mapping classes on multiple joined tables compatible with the use of ODMG? I ask because according to the documentation, auto-update must be set to true in order to achieve such a mapping, however, ODMG is only guaranteed to work with auto-update set to false. Thanks in advance, Luis

Re: Hibernate don't manage locks bewtween several JVMs...

Hi Brian, I like that idea! It would put an end to that discussion. Thomas Brian McCallister wrote: It may be worthwhile to have database-lock pessimistic locking as a clearly labeled option (non-default) in order to cut short these periodic discussions =) I'd be all in favor of bundling a

reference-descriptor super question

Hello. I am using the reference-descriptor name=super option for mapping multiple joined tables. I have come across something that I can't figure out though. The example has Table A with ID and SomeValueFromA. It also has Table B with ID, aID, SomeValueFromB. It has B as the child A and the

Hibernate don't manage locks bewtween several JVMs...

Can you give me your opinions about answers i was given on the hibernate forum: http://forum.hibernate.org/viewtopic.php?t=930648 Thanks -- -NiX- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:

Sequencers in clustered environment

Hi, I've read the tutorial about how to work in a clustered environment, specially the part that has to be with sequencers. Using a Lock Column is a good solution, but as the nextVal cannot be rolled back, we would miss many possible codes. So I have implemented a sequencer that extends

Length attribute in OJB field descriptor

Hi, I was wondering which effect has the length attribute within field-descriptor in OJB. I have made a little test creating an object with its primary key longer than it should be. I have set the length attribute to the max length allowed in BD, but created an object with longer length in

Re: Setting addOrderByAscending() with foreign attribute

hi, first you have to have a relationship defined between classes of table a and classes of table b. then you you can use addOrderByAscending(relAtoB.name) where relAtoB is the name of the relationship. hth jakob [EMAIL PROTECTED] wrote: Hi all, I'd like to sort the result set based on a field

xdoclet foreign key requirements

I am attempting to use the @ojb tags and xdoclet to generate a torque schema for a project which isn't using ojb. I've found that they have these 2 requirements regarding foreign keys: 1. The table containing foreign keys needs to be a subclass of the primary key table 2. The number of foreign

Re: Hibernate don't manage locks bewtween several JVMs...

Hi NiX, Ojb provides several Locking strategies. You can use Optimistic locking based on versioning. Or you can use pessimistic locking. The pessimistic locking mechanism is implemented as a pluggable component. We ship two implementations: 1. an in-memory Lockmanager implementation that can be

Re: Hibernate don't manage locks bewtween several JVMs...

Hi NiX, Ojb provides several Locking strategies. You can use Optimistic locking based on versioning. Or you can use pessimistic locking. The pessimistic locking mechanism is implemented as a pluggable component. We ship two implementations: 1. an in-memory Lockmanager implementation that can be

Re: xdoclet foreign key requirements

On Mon, 10 May 2004, Mike Traum wrote: I am attempting to use the @ojb tags and xdoclet to generate a torque schema for a project which isn't using ojb. I've found that they have these 2 requirements regarding foreign keys: 1. The table containing foreign keys needs to be a subclass of the

Re: Hibernate don't manage locks bewtween several JVMs...

It may be worthwhile to have database-lock pessimistic locking as a clearly labeled option (non-default) in order to cut short these periodic discussions =) I'd be all in favor of bundling a DatabaseLockManager along with the current implementations. A fair number of people prefer this

Re: xdoclet foreign key requirements

Here's my example: -- BEGIN PARENT TABLE -- /** * @ojb.class table=USERPREFDEF * documentation=User Preference Definitions and User Preference Valid Value tables, which * allow specific preference options to be

OJB practices (best?)

I would like to know how other teams are using OJB, what their experiences have been, and some of the architecture decisions you have built around OJB. (I know this is not a pure OJB question, but I would like to help compile a list of common architecture approaches to help new people get started)

Re: Setting addOrderByAscending() with foreign attribute

Thanks Daniel, Origianlly I didn't want use referece-descriptor, but it has become apparent that I'd need it. I appreciate your help! Sincerely, Daehyun Daniel Perry wrote: addOrderByAscending(b.name); Make sure you use capitalisation as per your repository.xml - normally why things dont work

Re: Setting addOrderByAscending() with foreign attribute

Dear Jakob, Origianlly I didn't want use referece-descriptor, but it has become apparent that I'd need it. I appreciate your help! Sincerely, Daehyun Jakob Braeuchi wrote: hi, first you have to have a relationship defined between classes of table a and classes of table b. then you you can

Re: Inconsistence in Persistence Broker

Hi, difficult to analyse what's going wrong. Are there associations between Employee, Department and Role? If yes, do you set auto-update 'true' or 'object'? Do you change any settings in OJB.properties file? Do you use one PB instance per thread (PB instances are not threadsafe)? regards,

Re: Old data are returned

Nicolai Krog wrote: Hi Armin, WOW, thanks! You were right; I changed the object-cache implementation to ObjectCachePerBrokerImpl (it was the ObjectCacheDefaultImpl before), and the problem vanished! :-D This was REALLY nice of course, but the whole thing has made me sweat a bit; my

Re: Child Table insert at same time as Parent and Auto generated PK

Hi Mark, java.lang.ClassCastException at org.apache.ojb.broker.metadata.MetadataManager.buildDefaultKey( MetadataManager.java:558) at org.apache.ojb.broker.metadata.MetadataManager.init( MetadataManager.java:164) at Here is the source code: private PBKey buildDefaultKey() { List

Re: Child Table insert at same time as Parent and Auto generated PK

No there is only one jar file which is wrapped into the .war file that is deployed. Mark Armin Waibel [EMAIL PROTECTED] wrote: Hi Mark, java.lang.ClassCastException at org.apache.ojb.broker.metadata.MetadataManager.buildDefaultKey( MetadataManager.java:558) at

Re: Hibernate don't manage locks bewtween several JVMs...

I have gotten a great deal of value out of this thread. I am a novice OJB user compared to all of you but find OJB to be pretty darn good and well thought out. Hibernate seems to have a lot of PR and attention. But that doesn't make it the best choice. What I would like to do is have a

Re: Child Table insert at same time as Parent and Auto generated PK

Mark Spritzler wrote: root cause java.lang.ExceptionInInitializerError at org.apache.ojb.broker.core.PersistenceBrokerFactoryBaseImpl.getDefaultKey(PersistenceBrokerFactoryBaseImpl.java:75) at

[JDO] JDO and application server.

Hi, We are developing an application server (a uPortal channel) and we use OJB-JDO in order to implement data persistence. Everything works fine when the application is accessed by one user. But as soon as the application is concurrently accessed by two (or more) users, multiple instances are

collection proxy gives sql error

sorry... not sure why i replied then... monday morning... Upgraded to RC6, and everything seemed to be fine. until now :) One bit of code (that grabs a list - proxied collection) causes some nasty sql errors. Upon calling the .size() method it generates some sql (I'll hazard a guess of a

RE: Setting addOrderByAscending() with foreign attribute

addOrderByAscending(b.name); Make sure you use capitalisation as per your repository.xml - normally why things dont work for me on first try! Daniel. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 10 May 2004 10:23 To: [EMAIL PROTECTED] Subject: Setting

RE: collection proxy gives sql error

It's ok... found the fix in BrokerHelper.java in cvs. Daniel. -Original Message- From: Daniel Perry [mailto:[EMAIL PROTECTED] Sent: 10 May 2004 12:35 To: OJB Users List Subject: collection proxy gives sql error sorry... not sure why i replied then... monday morning... Upgraded to RC6,

Re: [JDO] JDO and application server.

On 04/05/10 9:58, Alexandre BOISSEAU [EMAIL PROTECTED] wrote: Hi, We are developing an application server (a uPortal channel) and we use OJB-JDO in order to implement data persistence. Everything works fine when the application is accessed by one user. But as soon as the application is

Re: [JDO] JDO and application server.

Thanks Pedro, Yes, Currently, I use a single persistance manager for each user. I create it in the constructor and close it after the session is done.br I will try to create a PM for each job. br Alexandre. Pedro Salgado wrote: On 04/05/10 9:58, Alexandre BOISSEAU [EMAIL PROTECTED] wrote: