Have a look at the state diagrams in the spec - there is no reason for the
container to set the fields to null in BMP.
Tom
On Sat, 3 Mar 2001, David Castro Diephouse wrote:
> Looking at the code, this appears to be fixed in 2.1 (entity fields are set to
> null/0 in ejbCreate), for CMP anyway. No change for BMP.
>
> Larry Kline wrote:
>
> > I have a test program that creates entity beans with just their primary key
> > information, then sets each of their data fields, and finally deletes them.
> > I run this and everything works just fine. But if I stop the test in a
> > debugger after the creation step (and before I set the data fields), I
> > notice that the data fields have values in them also! It doesn't appear to
> > be total garbage. It looks like data from a previous run of the test. Is
> > this expected behavior? Is the app server or the database caching stuff
> > and when it sees the same primary key information it automatically
> > populates the data fields?
> >
> > I've even tried deleting the rows in the database that represent the beans
> > with SQL statements instead of deleting the beans as entity beans. Same
> > result.
> >
> > I'm using jBoss 2.0 FINAL running under jdk1.3 with Hypersonic database.
> >
> > - Larry
> > Larry Kline
> > [EMAIL PROTECTED]
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
>
>
--
"If you mess with something for long enough it will break." - Schmidt
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]