Hi Ben,

> Dear List,
> 
> O.k. so maybe we can use the persitance broker for our 
> commercial project.
> if there is no license issues. BUT could anyone comment on 
> the following
> project requirements, and say how effective ojb is to do the task ?
> 
> 1) Should be able to work with IBM DB2, SQLserver and ORACLE.

No problem with OJB, lots of people are using it with those DBs.

> 2) We want to store images into the database.

No problem with OJB. There is only one gotcha with the Oracle thin driver,
that has problems to work with BLOBs larger than 4K in a standard JDBC way.

> 3) we have some master-child-grandchild table relationships.  How
> problematical is this in the
> context of a multi-user OLTPsystem. 

Absolutely no problem with OJB. OJB supports polymorphism, inheritance,
complex mapping strategies etc., etc.

> To what extent does the 
> persistance
> layer deal with
> locking.

The OJB kernel provides Optimistic locking based on Versions and timestamps.
OJB_ODMG also provides pessimistic locking with a distributed lock engine
which allows to use lock across a cluster of OJB engines.

> 4) Should be JDO compliant.

in OJB 1.0 we provide a OjbSTore plugin. You can plug this component into
the JDORI and use OJB as a full fledged JDO implementation.
In 2.0 we will have our own clean room JDO implementation.

> i.e. that we can use to " sell " 
> future projects

You should check with Craig Russel from SUN if there are any problems in
using the JDO RI for your purpose.
SUN want to make it possible to use JDORI + OJB in commercial projects. The
more users request it, the sooner we will have a general permission.

> 
> Would appreciate any help. We are looking at Torque (5 hours 
> on friday night
> and still no correct installation!) which isnt a Java 
> standard, and we want
> asfar as possible, to implement a solution using skills that 
> we are likely
> to sell again.

> I must admit I was a little diconcerted to read a
> recomendation here to use another Object relational mapping 
> tool such as
> Hibernate ? Is this a common consensus. ?

I've never seen any recommendations for Hibernate on this list.
I see no reason to switch from OJB to Hibernate. 
I don't know of any Hibernate feature that OJB does not support as well.
In addition OJB is commited to support standard APIs like ODMG and JDO.

cheers,
Thomas

> 
> Appreciate any help.
> 
> Ben
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to