> No...
>
> The _guid property is private. I've overridden the
> toString() method to return a _guid.toString().
Ok, but an instance of a class have full access to private fields of
another instances of the same class.
Norton, could you show us the complete code for GUID class?
Bye,
Norton,
Your PK equals method:
public boolean equals(Object obj) {
GUID compareTo = (GUID)obj;
if (_guid.toString().equals(compareTo.toString())) {
return(true);
}
return(false);
}
The correct would be:
...
if (_guid.toString().equals(compareTo._guid.toString()
Hi, all...
On Thu, 17 May 2001, Leonard Kierstead wrote:
>
>
> |The workaround I found was to ignore i-net data sources and use
> |OPTA 2000 as a JDBC 2.0 Optional Package non-compliant driver:
>
> I'm not exactly sure what you mean by this. I'm guessing that by changing :
>com.inet.tds
Hi,
In EJB 1.1 specs I found that with CMP beans, primary key classes must
have a no-args constructor. But what about using Strings and Integers as
primary keys? They are allowed? Where, in the specs, I find this?
Thanks in advance,
Rafael
__
The workaround I found was to ignore i-net data sources and use
OPTA 2000 as a JDBC 2.0 Optional Package non-compliant driver:
oto25
org.opentools.minerva.jdbc.xa.wrapper.XADataSourceImpl
...
From the Minerva docs:
"You must determine whether your driver supports the JDBC 2.0
egacy application changing the database concurrently with
BMP beans, I will need to turn off the cache? How?
Thank you all.
Rafael
> --Victor
>
>
> Rafael Alves Chaves wrote:
>
> > Hi,
> >
> > I'm having a strange problem with entity beans in JBo
Hi,
I'm having a strange problem with entity beans in JBoss. For debugging
purposes, I have instrumented ALL callback and business methods to
generate an output identifying the called method and, when useful, its
arguments.
Below is the trace generated after two different clients are execu
Hi,
I'm trying to use the i-net OPTA 2000 4.0 for MS-SQL Server 2000
evaluation version (limited on two concurrent connections) with JBoss,
without success.
Every time my BMP beans try to close the database connection, the
following exception occurs:
javax.transaction.xa.XAException:
