All right, fair enough, maybe discouraging bug reporting was a bit over
the top...
Sorry. What I mean is that a lot of these bugs have been fixed. I think
we've got the cvs release mechanism more or less sorted, now just got to
implement it...
Tom
On Thu, 8 Mar 2001, David Castro Diephouse wrote:
> You know, for users to report bugs against the current release version is a
> pretty
> normal practice. Unless we want to say that there is NO current release
> version of
> jboss, just a current beta. We do claim on the website that 2.0 is the
> current
> release.
>
> That said, it is the case that we have not been backporting 2.1 bugfixes to
> 2.0
> Final. This is one of the reasons that people keep asking when the next
> release will
> be - so they dont have to upgrade to a beta, which is unacceptable to the
> majority of
> users.
>
> Tom Cook wrote:
>
> > You are reporting lots of bugs against 2.0 final - the code base has moved
> > considerably since then. You really need to get a more recent version.
> >
> > Tom
> >
> > On Thu, 8 Mar 2001, James Cook wrote:
> >
> > > In our ejbLoad we are all accustomed to calling:
> > >
> > > PK key = (PK)this.entityContext.getPrimaryKey();
> > >
> > > We do this because the bean's attributes are not yet set and the
> container will
> > > use the entitycontext to pass the pk.
> > >
> > > In ejbRemove(), we do not have to resort to this step because the bean's
> > > attributes will be set with a call to ejbLoad() in the case of commit
> options B
> > > and C.
> > >
> > > But how do we execute ejbRemove() when using commit option A? When using
> commit
> > > option A, the bean is *not* synced with the db because ejbLoad() does
> not fire.
> > > The container however must ensure that you get the appropriate bean
> instance
> > > that matches the PK you wish. So if I do:
> > >
> > > MyRemote remote = getMyHome().findByPrimaryKey(pk);
> > > remote.remove();
> > >
> > > the FBPK method should return a remote reference to the bean in the
> ready pool
> > > that matches the pk value I pass in, if it exists already. If it does,
> ejbLoad()
> > > is not called. However, when I invoke remote.remove(), the pk attribute
> of the
> > > bean is null!? This appears to be a bug.
> > >
> > > jim
> > >
> > >
> > >
> > >
> > >
> > > --
> > > --------------------------------------------------------------
> > > 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]
>
>
>
>
>
> ---------------------------------------------------------------------
> This message (including any attachments) contains confidential, proprietary
> or privileged information intended for a specific purpose and individual(s),
> and is protected by law. If you receive this message in error, please
> immediately delete it and all copies of it from your system, destroy any
> hard copies of it and notify the sender. Any unauthorized disclosure,
> copying or distribution of any part of this message, or the taking of any
> unauthorized action based on it, is strictly prohibited.
>
>
> --
> --------------------------------------------------------------
> 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]
