[EMAIL PROTECTED] wrote:
>
> Thanks for the response. Here is some basic info about the bean.
>
> (The one thing I did not mention is that this Bean was working just as
> it should until the upgrade to 2.1!)
> The transactional attribute is none.
> Using RMI.
> Client is an applet.
> Normally the first place I go is the code. The way ejbStore and
> ejbLoad fire off under 2.1 seems to be much different than 2.0.
>
> The problem is the following. (And this is with just one user on the
> system) I log into the application. There is a button to create a new
> story in the system. You click on it and you get what you would
> expect: A blank story screen. On the back end, ejbCreate has been
> called on the entity and a minimal entry is placed into the database.
> There are basically 5-6 columns of information in the db that the
> entity maps too. If you leave one of those columns blank, through
> successive passivate and ejbLoad calls, one of the fields mysteriously
> get filled in with data from another record in the DB. It is like the
> primary key is screwed up or something. Below is the PK code for
> reference.
> public class StoryPK implements Serializable
> {
> public StoryPK()
> {
> }
>
> public int hashCode()
> {
> return storyId;
> }
>
> public boolean equals(Object other)
> {
> boolean isEqual = false;
> if (other instanceof StoryPK)
> {
> isEqual = (storyId == ((StoryPK)other).storyId);
> }
> return(isEqual);
> }
> public int storyId;
> }
>
> John
Thanks John,
as you told me, the weird bahavior disappear as soon as
all the entity variables are correctly initialized.
We can conclude it's not a bug in JOnAS 2.1.1
Best regards,
--
Philippe
Philippe Coq Evidian Phone: (33) 04 76 29 78 49
Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
Download our EJBServer at http://www.objectweb.org
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
