Re: IllegalAccess error setting field in db-ojb-1.0.3

Hi Rajesh, Rajesh T V wrote: Hi Armin, Thanks for your reply.Reply inline. -Rajesh does OJB log a more detailed error message? no Please search for this message in your log file again. If you use OJB 1.0.3 or higher OJB will log a detailed error message before the exception was thrown.

Re: inner join n:1 how to

Hi, [EMAIL PROTECTED] wrote: Normally , if i use QueryByCriteria q = QueryFactory.newQuery(ProductImpl.class, criteria); and criteria contained some ProductGroup conditions ; and then i will retrieve all data of ProductImpl that product table outter join with ProductGroup table . May be in this

Re: standalone getDefaultBroker auto-retrieve

Yep. I did something like... with an immediate catched exception!! it works... I add a method into PersistenceBrokerFactory to artificially fire all the finalize methods. This method call releaseAllInstances and System.gc(). then Finalize are all fired. It works well. Will release 1.0.5 come out

Re: Procedure based sequencence generator repeating values

Hi! I'm still with this problem. Could someone say if SequenceManagers use default connection present at current thread? Or it's executed inside same transaction (I don't know if this implies same connection)? Thanks for any clarifications! Richter Edson Carlos Ericksson Richter

Re: Problem joining two tables with same column name

Hi, Does anyone have the solution for this? Do mail to the following id [EMAIL PROTECTED] Thanks Neha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Procedure based sequencence generator repeating values

Ok, guys: now, I'm lost! I changed auto-commit from 1 to 2, and now, appear OJB is trying to insert records twice - on every new object I store, I get primary key violation! I'm using PB API with MsSQL Server 2000 SP4 and JDBC Driver for MS SQL Server 2005 latest release. Someone knows what

Re: standalone getDefaultBroker auto-retrieve

Hi Armin, The detection mechanism works, but i have a strange behaviour, i collected some open-broker detections. So i had a look into code, and i saw my close call in a finally clause. this is correct. So, i don't doubt about java finally, but the implementation of my closeBroker method. In

Re: Procedure based sequencence generator repeating values (MAYBE SOLVED)

Ok, guys. I think I discovered a piece of solution for this problem: 1) Database must be in Full recovery model 2) Every trigger must start with SET NOCOUNT ON and end with SET NOCOUNT OFF 3) The OBJ_NEXTVAL_PROC should start with SET NOCOUNT OFF We are in testing fase right now, but appear the

Re: Returning DynaBeans

hi phil, we could return DynaBeans for ReportQueries instead of Object[]. i'm not sure if DynaBeans are useful for normal queries. jakob Armin Waibel wrote: Hi Phil, [EMAIL PROTECTED] wrote: I am interested in finding out more information about OJB's support of the commons-beanutils