Re: OJB-JDO why sequence increment in retrieve

2005-05-19 Thread Alessandro Vincelli
Ok, I'am trying in other ways, but I have other problems. Can you hel me in a correct ... Identity oid = new Identity(e, broker); ... b = (Utenti) persistenceManager.getObjectById(oid, false); ... thanks in advance Armin Waibel ha scritto: Hi Alessandro, Alessandro Vincelli wrote: I use

Re: OJB-JDO why sequence increment in retrieve

2005-05-19 Thread Armin Waibel
= broker.serviceIdentity().buildIdentity(...) this method allows to build Identity objects based on a object itself or on the used PK. If you want to use JDO-api in production environment I recommend to use JPOX, because OJB-JDO is only a prototype based on jdori (JDO2.0 will be supported in OJB2.0

Re: OJB-JDO why sequence increment in retrieve

2005-05-18 Thread Martin Kalén
Alessandro Vincelli wrote: I have tried, but I have had great problems. Tomcat always says: Message: Scheduler with name 'Cocoon' already exists. This is only the effect of a previous error. Cocoon has the following web.xml configuration: load-on-startup1/load-on-startup This means that Tomcat

Re: OJB-JDO why sequence increment in retrieve

2005-05-12 Thread Armin Waibel
Hi Alessandro, Alessandro Vincelli wrote: I use this simple code to retrieve row, but after this code the db sequence of Utenti table is autoincrement. Why? Thanks,Ale //1. Get the PersistenceManager PersistenceManager persistenceManager = jdo.getPersistenceManager(); Utenti e

Re: OJB-JDO why sequence increment in retrieve

2005-05-09 Thread Alessandro Vincelli
I use db-ojb-1.0.1 with cocoon 2.1.7 Can i try the new latest release with cocoon? Thanks a lot Gallardo I use with great satisfaction Druid. I have read all what you have made on OJB/JDO/CForms. Antonio Gallardo ha scritto: Hi: Please provide the OJB version you use. AFAIK

Re: OJB-JDO why sequence increment in retrieve

2005-05-09 Thread Alessandro Vincelli
Hi I have a problem to include db-ojb1.0.3 in Cocoon 2.1.7 build with jdk.1.5 Can I compile db-ojb1.0.3 with jdk.1.5 and include this in Cocoon? Thanks a lot I receive this message: Initialization Problem Message: Scheduler with name 'Cocoon' already exists. Description:

Re: OJB-JDO why sequence increment in retrieve

2005-05-09 Thread Antonio Gallardo
On Lun, 9 de Mayo de 2005, 2:45, Alessandro Vincelli dijo: I use db-ojb-1.0.1 with cocoon 2.1.7 Can i try the new latest release with cocoon? Yep. Thanks a lot Gallardo I use with great satisfaction Druid. I have read all what you have made on OJB/JDO/CForms. :-) I am glad to hear

Re: OJB-JDO why sequence increment in retrieve

2005-05-09 Thread Antonio Gallardo
On Mar, 10 de Mayo de 2005, 12:28, Alessandro Vincelli dijo: Hi I have a problem to include db-ojb1.0.3 in Cocoon 2.1.7 build with jdk.1.5 Can I compile db-ojb1.0.3 with jdk.1.5 and include this in Cocoon? I guess yes. I will try to add this to the cocoon svn today night. Best Regards,

Re: OJB-JDO why sequence increment in retrieve

2005-05-09 Thread Alessandro Vincelli
I have tried, but I have had great problems. Tomcat always says: Message: Scheduler with name 'Cocoon' already exists. Description: org.apache.avalon.framework.configuration.ConfigurationException: cannot create a quartz scheduler Sender: org.apache.cocoon.servlet.CocoonServlet Source:

OJB-JDO why sequence increment in retrieve

2005-05-08 Thread Alessandro Vincelli
I use this simple code to retrieve row, but after this code the db sequence of Utenti table is autoincrement. Why? Thanks,Ale //1. Get the PersistenceManager PersistenceManager persistenceManager = jdo.getPersistenceManager(); Utenti e = new Utenti();

Re: OJB-JDO why sequence increment in retrieve

2005-05-08 Thread Antonio Gallardo
Hi: Please provide the OJB version you use. AFAIK, it was already fixed for non JDO API's. Best Regards, Antonio Gallardo On Lun, 9 de Mayo de 2005, 18:15, Alessandro Vincelli dijo: I use this simple code to retrieve row, but after this code the db sequence of Utenti table is autoincrement.

OJB/JDO

2004-07-29 Thread Artur Z
hello I searched the archive and I have not found answers so please tell me: - is it still impossible to use OJB/JDO in production (because of the sun's JDORI license) ? - when apache implementation of JDO will be ready ? - why JDO api is better than ODMG (I mean functionality, usability

Re: OJB/JDO

2004-07-29 Thread Brian McCallister
On Jul 29, 2004, at 4:42 PM, Artur Z wrote: hello I searched the archive and I have not found answers so please tell me: - is it still impossible to use OJB/JDO in production (because of the sun's JDORI license) ? Yes - when apache implementation of JDO will be ready ? Good question. We

Re: OJB/JDO

2004-07-29 Thread Artur Z
Subject: Re: OJB/JDO On Jul 29, 2004, at 4:42 PM, Artur Z wrote: hello I searched the archive and I have not found answers so please tell me: - is it still impossible to use OJB/JDO in production (because of the sun's JDORI license) ? Yes - when apache implementation of JDO

Re: OJB/JDO

2004-07-29 Thread Brian McCallister
everything. In other words, it is a best guess on my part. -Brian Artur - Original Message - From: Brian McCallister [EMAIL PROTECTED] To: OJB Users List [EMAIL PROTECTED] Sent: Thursday, July 29, 2004 11:27 PM Subject: Re: OJB/JDO On Jul 29, 2004, at 4:42 PM, Artur Z wrote: hello I searched

Problem with OJB-JDO plugin and proxy classes

2004-05-04 Thread Alexandre BOISSEAU
Hi, I have problems when using proxy class : With the tutorial example : Loading of Article objects for a given ProductGroup works correctly, but when I try to load Article objects only, the search always returns nothing. Removing proxy from Article class-descriptor fixes the problem (search

Re: Problem with OJB-JDO plugin and proxy classes

2004-05-04 Thread Brian McCallister
I believe, though lack first hand knowledge, that Thomas M. said the JDORI plugin doesn't work with proxies. That is its big drawback =( -Brian On May 4, 2004, at 4:16 AM, Alexandre BOISSEAU wrote: Hi, I have problems when using proxy class : With the tutorial example : Loading of Article

How to set up a ojb-jdo project

2003-12-10 Thread Sebastian Münch
Hi, we are in the middle of developing a small application using the jdo api on ojb. The tutorials are running fine, now we wanna setup our own app. By compiling our application, we get the following error: [JDO] DEBUG: OjbStoreConnector.begin: connectionReadyForRelease=false

Re: How to set up a ojb-jdo project

2003-12-10 Thread Gus Heck
This looks like a runtime error not a compile time error. This exception means, as you guessed, that either you forgot to enhance the class (with the sun reference enhancer), or the enhancer tried and failed (you should get messages if it fails). Alternately, you have inadvertently tried to

[ojb|jdo] Join query using jdo/ojb

2003-11-19 Thread Vijay
Hello all, I was going through some documents related to JDOQL and I found that they have made the db-objects with other db-objects as attributes for maintaining foreign key relationship. Example: Employee object represents the Employee table in the database. It has a attribute department. Now

OJB JDO multiple database

2003-10-29 Thread Christophe.Demarey
Hi, Is there a way how I can simultaneously use multiple databases from OJB JDO ? OJB allows us to specify multiple jdbc-connection in the database repository but I don't know how to choose a jdbc-connection via the OJB JDO api ? I wonder if the following JDO code works with OJB

Re: Problems with OJB JDO

2003-03-23 Thread Thomas Mahler
You must enhance the byte-code of the tutorial app. I assume you just forget the ant target enhance-jdori. (See first section of tutorial4.html). cheers, Thomas Gary Eberhart wrote: Hello All, I'm getting the following exception when running the OBJ JDO example UCListAllProducts. Any ideas?

Problems with OJB JDO

2003-03-21 Thread Gary Eberhart
Hello All, I'm getting the following exception when running the OBJ JDO example UCListAllProducts. Any ideas? javax.jdo.JDOUserException: Class given to getExtent does not implement javax.jdo.spi.PersistenceCapable at com.sun.jdori.common.PersistenceManagerImpl.getExtent(Unknown Source)